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 |
|
shiyam198
Yak Posting Veteran
94 Posts |
 Posted - 2013-09-17 : 11:58:56
|
| Hi,We setup Windows Snapshots on the Windows Server (VM) that runs SQL server 2008.It hosts databases for a reporting application. So, 90% of the queries are reads and the rest are writes to a log database.I see significant slowness on this server after I restored the databases on the server. The queries (read) that usually take 1 to 4 seconds now take 35 seconds.I see there is a snapshot setup on this server on the OS (Windows) level.Could this be a reason?Thanks for your input.- Shiyam |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2013-09-17 : 12:46:41
|
| I don't know anything about Windows snapshots, but I would take a step back. Have you checked the execution plan? Have you updated statistics on the tables? Is there a hardware bottleneck such as CPU or I/O? What do the wait stats show?Tara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/ |
 |
|
|
shiyam198
Yak Posting Veteran
94 Posts |
Posted - 2013-09-17 : 14:14:05
|
| I did check the Profiler and found the most expensive query on the web request. The same query that has the same version of the application and the databases runs in less than a second.Even in this staging environment, I ran the test web request and it was much faster. It is only after the restore of 2 databases (only one being the main dataastore) and a cube, it started being slow. from less than a second to 35 second. Now if I restore the old databases that were on this server, it is still 35 seconds. Which means the issue is not on the databases, can't be on the server because before the restores it worked fine.So, only thing I can think of it is the VM (Virtual Machine) snapshots that is kept for this Database server.Am I wrong?- Shiyam |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2013-09-17 : 15:06:42
|
| It did not mean that it's not the databases. Statistics! Update the statistics on the tables involved. How big are they? Maybe do a fullscan.Tara KizerSQL Server MVP since 2007http://weblogs.sqlteam.com/tarad/ |
|
|
|
|
|
|
VM Snapshots on the server that hosts SQL server