On Mar 27, 12:32pm, "Tom Cooper"
<tomcoo...@comcast.no.spam.please.net> wrote:
> You don't mention which release of SQL you are on. If you are on SQL 2005
> and a version of Windows that makes "Instant Initialization" available, you
> might want to consider using it. Kimberly Tripp has a good discussion of
> this feature (including why you might not want to use it) athttp://www.sqlskills.com/blogs/kimberly/2007/03/04/InstantInitializat...
>
> Tom
>
> "NC3" <ncolem...@yahoo.com> wrote in message
>
> news:2b5a9b35-78cc-4f7b-bad1-47274a608b55@a1g2000hsb.googlegroups.com...
>
>
>
> >I have a 52 GB database that take 3 hours to restore using SQL Server
> > native restore. Does this seem long to anyone who has experience with
> > databses of this size? I know each insatalltion is different so things
> > like this can vary.
>
> > The hardware specs don't seem to matter much because I've restored the
> > database on hardware with different specs but the restore times are
> > consistent. The database is a publisher in a trasnactional replciation
> > topology and I don't know if that matters or not.
>
> > the hardware is our environment for SQL is generally the same dual 2/8
> > Ghz with 4 to 8 gb or RAM. We do use SATA drives which I understand
> > are slower drives but I'm not the sys admin guru.
>
> > any insught is appreciated.- Hide quoted text -
>
> - Show quoted text -

I'm using SQL 2005 sp2 on Windows 2003 sp1. Thanks for the reference
I'll be sure to give it a read.