An alternate method is to "detach" the database on the source PC, copy the
actual .mdf and .ldf files to the target PC, then "attach" the database on
the target PC. It accomplishes the same thing as backup and restore, but
detach and attach take less time than backup and restore. There is a lot of
documentation out there on how to do this. Start by going to
search.microsoft.com and searching on "detach database" and "attach
database"

Signature
Kent T. Stuver, President
Nanjimi Group, Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Stop Money Worries NOW!!
Reduce your debt, create excess cash for
investing, and build an ongoing, passive income.
Click NOW==> http://www.controlyourcashflow.com/2/
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Create a new database with the same name and then copy the backup data files
> onto the ones just created.
[quoted text clipped - 27 lines]
> > REALLY don't want to lose everything on those files. Is
> > there some procedure I'm not following. Any ideas ????
tsp - 22 Sep 2003 03:44 GMT
Thanks Brian for suggesting copying the database. That
idea sent me down the path of doing the DETACH and ATTACH
that Kent subsequently suggested when SQL7 would not let
me copy over one of it's files without the DETACH.
I ran the DETACH and ATTACH SP's from the 'masterdb'. It
worked fine but I wasn't sure if there was a better way.
I have my files back and functional.
I'm new but learning more about this beast every day with
your help.
Thanks Brian and Kent for your help !!!!
>-----Original Message-----
>An alternate method is to "detach" the database on the source PC, copy the
[quoted text clipped - 39 lines]
>
>.