July 7, 2009 at 10:44 pm
Situation is that a database used to be able to parse files in very fast. With no known changes the parsing that used to take seconds is now taking minutes. For example 10 seconds to now 6 minutes... as you could see this would be a problem. I have used the profiler to try and track down the slowness, as if it was a index or something along those lines. it turns out the only slowness I can see in the profile trace is when it tried to do the IF @@TRANCOUNT > 0 COMMIT TRAN. This is really the only slowness. When this happens what is actualy happening, an were will my problem likely be found and solved? Any suggestions or help is welcomed.
Thanks in advance!
July 8, 2009 at 8:32 am
It would be much easier to help you out if you posted the code. The snippet you have posted should not be causing any performance issues as it is not reading from a table, just doing a comparison.
Have you looked at blocking using sp_who/sp_who2 and sp_lock? Can you run performance monitor to check CPU use, Blocking, etc...?
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
July 12, 2009 at 2:11 pm
JACK,
Thanks for responding to my post. I have the issue resolved. The problem was a low battery on one of the RAID controllers, LOW BATTERY!, What a POS, who would think a low battery could cause I/O issues and not leave even a trace in the logs, but affect performance as much as it was. At anyrate once the battery was replaced the server was humming right along. Thanks for the input.
Richter
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply