Please start any new threads on our new site at We've got lots of great SQL Server experts to answer whatever question you can come up with.

Our new SQL Server Forums are live! Come on over! We've restricted the ability to create new threads on these forums.

SQL Server Forums
Profile | Active Topics | Members | Search | Forum FAQ
Save Password
Forgot your Password?

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 Restore of 20 gb .bak
 Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

Yak Posting Veteran

90 Posts

Posted - 02/20/2006 :  23:37:31  Show Profile  Reply with Quote
I have a 20gb backup of a database that I'm trying to restore from a SQL Server 2000 DB to my new SQL Server 2005 DB on my new server. This restore is taking forever. How can I speed up the process?

The server is an HP with :

3.6 Xeon Hyperthreaded Processor


or is this just expected for a database of this size to take over an hour to restore?

Flowing Fount of Yak Knowledge

3575 Posts

Posted - 02/21/2006 :  00:34:37  Show Profile  Reply with Quote
are you restoring from a network share? are you restoring from a file that is on the same disk as the database datafiles? How are your disks configured?

Go to Top of Page


United Kingdom
1870 Posts

Posted - 02/21/2006 :  04:01:14  Show Profile  Visit mr_mist's Homepage  Reply with Quote
This will have more dependency on your disk architecture than anything else. If you're finding it's taking an excessive time consider improving your hardware setup.

Moo. :)
Go to Top of Page

Flowing Fount of Yak Knowledge

United Kingdom
1168 Posts

Posted - 02/21/2006 :  05:27:39  Show Profile  Reply with Quote
Is the backup a single file, or multiple files? I recall getting performance improvements at a previous client when having the backup across multiple files (we had a 180 GB db back then).

Further to Eyechart's question - you don't want to do this across a network (in my experience).

Ideally you want to be restoring from "drive A" to "drive B" - and if that's a SAN, hopefully those aren't charing disks...

*##* *##* *##* *##*

Chaos, Disorder and Panic ... my work is done here!
Go to Top of Page


United Kingdom
22859 Posts

Posted - 02/21/2006 :  08:07:34  Show Profile  Reply with Quote
Perhaps the original database had LOADS of spare slack space - SQL Server will re-create all that slack and then restore the database into it. It may also be a backup from something with a huge transaction log which had not been cleared down ... I've known restores from those scenarios to take much longer than one would expect

If that's likely you might want to consider getting at the original database and "shrinking it" and then backing it up - assuming that that is possible (and taking into account the normal caveats about shrinking production databases!)

Go to Top of Page
  Previous Topic Topic Next Topic  
 Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.03 seconds. Powered By: Snitz Forums 2000