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 |
|
pavanai
Starting Member
1 Post |
 Posted - 2009-06-29 : 03:07:53
|
| Hi,I am doing performance testing on our product which has SQL server 2005 as back end. I see high response time for my transactions during 12:00 AM EST--5 AM EST. Only SQL counter which has similar high values during that time window is full scans/sec(in thousands). DB team has confirmed that there are no jobs running in the server at that time. Once its past 5:00 am the same tests will run almost five times faster and the average full scans/sec value will also drop to 1-2 per second. If i dont run any tests in that time window the full scans/sec will remain very low. Any idea about the issue here?RegardsPavi |
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
Posted - 2009-06-29 : 03:15:45
|
quote:
This counter indicates how often a table index is not being used and results in sequential I/O.This is defined as the number of unrestricted full scans. These can be either base table or full index scans.Missing or incorrect indexes can result in reduced performance because of too high disk access.
The explanation is that something is running during these hours.Please have your DB team check not only for Jobs, but also for Maintenance plans.Most often the 12am-5am window is used for maintenance tasks.
E 12°55'05.63"N 56°04'39.26" |
 |
|
|
|
|
|
High values for full scans/sec