Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
avinashily
Starting Member
10 Posts |
 Posted - 2010-11-17 : 03:02:21
|
| hi,we are having few databases in sql server 2005 running on windows 2000 server where users always complain that the every day just around break times every one feels the slowness and they can not save the records to the database or able to view them. either it takes a lot of time for them to view it or else they will get timeout expired error. i have tried to get the culprit by running the profiler and then saw that there were few statements in the trace file which ran for more duration say about more than 50ms. in ordinary times the same statement if ran was taking 1ms. i have passed the trace file as a workload to the dts and created the recomended indexes but it made no difference. can someone suggest me how can i approach the problem in a better way and catch the culprit. |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2010-11-17 : 09:03:20
|
| Check for blocking during these times, using sp_who2.Identify the poorly performing queries and look at the execution plans. See if they can be optimized, or if new indexes will help.When is the last time indexes were rebuilt?Turn on perfmon and look at CPU utilization, disk queue length and page life expectancy at a minimum.Is anything else running on the server besides sql?Any jobs that run during these times?What makes these particular times different than any other time? That is the first thing u need to identify |
 |
|
|
Kristen
Test
22859 Posts |
Posted - 2010-11-17 : 13:06:30
|
| "Is anything else running on the server besides sql?Any jobs that run during these times?"Virus Scan perhaps? |
|
|
|
|
|
|
database is slow at certain times every day