July 2, 2013 at 9:42 pm
I have a 2005 SQL server running about 20 databases identical in design. Each database is accessed by one or 2 users simultaneously. Performance is fine for all except 1 database. The size of the files are relatively small compared to all of the other databases files. Each database is accessed from the same terminal server so I know the problem is not a workstation issue. Running a query to get sysprocesses sorting bu CPU shows a wait type of SOS_SCHEDULER_YIELD and the cmd is SELECT when accessing that database.
Any suggestions on how to go about troubleshooting this performance issue would be greatly appreciated.
July 3, 2013 at 10:24 am
Identified the offending SELECT statement. Now trying to figure out why this SELECT statement runs slower on this database than it does on all the others.
July 4, 2013 at 5:38 am
Try a profiler run to capture poorly performing statements. Also use PerfMon and Task Manager to capture performance metrics. Your indications suggest CPU issues. Find bad query(s) and tune appropriately. One possible thing is out of date stats leading to bad plan. Another is someone dropped an index (or one is needed due to data skew, etc).
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
July 12, 2013 at 9:28 am
As you already identified the SELECT statement check the indexes on all referenced tables.
Don't forget to check the overall server performance. SOS_SCHEDULER_YIELD could be a hint that the processor is busy. Maybe not the database is the problem but other processes on the server so that there are not enough ressources left for sql server.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply