May 19, 2009 at 3:09 am
waiting for the reply............
May 19, 2009 at 5:33 am
What reply are you waiting for?
It sounds like you need to carry out a generic performance tuning exercise on your platform.
I would concentrate on identifying the specific queries that are consuming the most CPU and then optimising them accordingly.
You need to qualify what is consuming the CPU.
If it is indeed SQL Server queries then you need to investigate further in order to identify which specific queries are responsible.
John detailed what to look for. If you can't change the query and you can't change the indexes, then you'll just have to be satisfied with the performance, as there's little else that will help. There's no magic setting that will make poor code run well.
Why can't the cursors, queries and triggers be changed? Fixing bad code is the number one thing to do when there's bad performance.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
May 22, 2009 at 1:20 am
thkz for the comments gail... gail i have changed many queries and cursors ... but still there is a performance degredation and 1 more i will like to know when all the process gets complted when i check from the task manager sqlserver not automatically release the memory... can u expalin this gail....
May 22, 2009 at 2:57 am
SQL will never release memory. Once it's allocated it will only release if the OS signals that the entire system is short of memory.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
May 22, 2009 at 5:15 am
Gail wat about pagefile ... even the process gets completes pagfile shows 11 GB
May 22, 2009 at 5:58 am
Gail wen i check the memory it still shows alloacated 10 GB even if there are no process is going on... if i restart the services it realse the memory
May 22, 2009 at 6:13 am
As I already said, SQL will not automatically release memory. Don't worry about the memory. You have plenty (16GB), SQL's using 10 or so, that's quite normal and not a problem.
Focus on finding problematic queries.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 7 posts - 16 through 21 (of 21 total)
You must be logged in to reply to this topic. Login to reply