up vote 0 down vote favorite
share [g+] share [fb]

I have a sql database and an application that runs on 2 different servers. These servers are running sql server 7 and are running the same version of the application.

One of the servers has started slowing down how long it was processing files, so we upped the amount of RAM from 2GB to 4GB, but this didn't help. All of the slow down occurs in the database as it goes through triggers to update tables.

It takes about 1.5 minutes for it to process a file (For reference, it takes the other server about 16 seconds to go through the same triggers and process a file).

I'm looking at the server that is taking forever and all of the metrics look good: There's enough ram (especially now that it's been upped to 4GB), the processor load is fine, etc etc.

Since it doesn't look like it's a resource issue and it's obviously not a trigger issue because both servers have exactly the same ones, I'm at a complete loss of what could be causing this...

link|improve this question
Have you watched the execution in activity monitor to see if it has some waits or blocking? – Dustin Laine May 5 '11 at 16:17
1  
@Dustin activity monitor probably doesn't exist for SQL Server 7 @user What is the trigger code? Also what do you mean by processing a file? – Martin Smith May 5 '11 at 16:20
SQL Server 7 might not use the extra RAM please take a look at this support.microsoft.com/kb/274750 – Beatles1692 May 5 '11 at 16:25
@Martin - Sorry, by processing a file I just mean going through all of the triggers to update necessary tables/columns and creating the audit trail (the main functionality of the app is file transfer). @Beatles - On the slow server (1.5 minutes to go through a file) it's actually set to use 3.5GB of the 4GB of memory. On the fast one (16 seconds to go through a file) it's set to use 2GB (out of the 2GB There) – user80515 May 5 '11 at 16:27
feedback

migrated from stackoverflow.com May 5 '11 at 16:23

This question came from our site for professional and enthusiast programmers.

1 Answer

up vote 0 down vote

i don't know anything about sql server 7, so i'm jsut going to go off of what i know about 200/2005+

have you checked to make sure that the max memory setting is set to an appropriate amount for the new ram?

have you tried refreshing views? refreshing views

have you made sure that the hardware, in all aspects, is the same on each server?

have you checked indexes/statistics?

link|improve this answer
I'd agree with this, except that I would put 'Check Statistics' at the top of the list. Check out the sp_updatestats command. – sgmoore May 5 '11 at 19:21
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.