Post reply

Restored database seems faster than the production version (under the same conditions)

  • January 29, 2008 at 7:49 pm

    #181421

    Hi,

    I have a web application (ASP.NET 2.0) connecting to a sql server 2005 instance (SP2) residing on the same server. I recently restored a fresh backup of the live database in the the same sql server instance as a new database (essentially duplicated the database). I also duplicated the web site to perform some tests on this restored database. Both databases have same content, are on the same instance and physical files are on the same disk.

    On a given page in the web app (many select statements are issued to generate this page), i consistently have about 3 times the performance using the restored database instead of the live one, even when the live database is idle (no requests from the production web site).

    Any ideas why a restored database would be faster ? I tried rebuilding indexes on the live database but the performance gap stays the same.

    Thanks for any pointers

  • January 30, 2008 at 8:25 am

    #773331

    There are many possible reasons, but the first that pops to my mind is that the original db might be using old execution plans. On 1 of the procs in question, issue a sp_recompile. You can also update stats, usage, etc.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply