Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Poor performance from single database Expand / Collapse
Author
Message
Posted Tuesday, July 2, 2013 9:42 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, May 21, 2014 12:03 PM
Points: 4, Visits: 23
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.
Post #1469836
Posted Wednesday, July 3, 2013 10:24 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, May 21, 2014 12:03 PM
Points: 4, Visits: 23
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.
Post #1470154
Posted Thursday, July 4, 2013 5:38 AM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Today @ 3:07 PM
Points: 4,356, Visits: 6,189
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 at GMail
Post #1470412
Posted Friday, July 12, 2013 9:28 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, August 29, 2014 5:21 AM
Points: 197, Visits: 730
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.
Post #1473108
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse