http://sqldbaoncall.com Thu, 08 Apr 2010 20:55:20 +0000 http://wordpress.org/?v=2.9.1 en hourly 1 Snapshots http://sqldbaoncall.com/snapshots/ http://sqldbaoncall.com/snapshots/#comments Thu, 08 Apr 2010 20:48:19 +0000 admin http://sqldbaoncall.com/?p=89 Client called,   application response dropped from 5 sec. to 2 min.  We profiled traffic,  60% statements  related to historical reports. Likely client has 2 Enterprise edition SQL2005

We set data mirroring between servers and on mirrored server created sql agent job Every 15 minutes drop and recreate database snapshot. Then redirected all historical reports to point on database snapshot.  Current application response time bellow 1 sec.

Current report execution time 10 sec.

]]> http://sqldbaoncall.com/snapshots/feed/ 0 Restore msdb from different server http://sqldbaoncall.com/hello-world/ http://sqldbaoncall.com/hello-world/#comments Sat, 03 Apr 2010 21:51:35 +0000 admin http://sqldbaoncall.com/?p=1 Few days ago I got emergency call. Company  restored  msdb from sql 2005  server A to server B. Everthing was working fine till application started to call SSIS  using shell. Production server was rebooted several time , same result.

I looked at sqlagent log file and found error  “Subsystem ‘CmdExec’ could not be loaded“,  2  minutes later perfect solution was found

http://blogs.infosupport.com/blogs/bertrand/archive/2007/11/14/Restoring-MSDB-across-instances_2C00_-a-bad-idea.aspx

]]> http://sqldbaoncall.com/hello-world/feed/ 0