Nice, however, questioner says "no .bak files, no detaching cause it's a
production thing"
--
Ekrem Önsoy
MCBDA, MCTS: SQL Server 2005, MCSD.Net, MCSE, MCT
[quoted text, click to view] "Erik G" <info@fdaregulatory.com> wrote in message
news:1189794209.610798.315310@22g2000hsm.googlegroups.com...
> If you can schedule downtime on production you can first do a full
> backup of prod, detach prod , copy to test (not move), Attach them
> both again. Rename test database to what ever you want. this is the
> fastest and most reliable. or you can backup prod, look at the BOL
> help for RESTORE DATABASE and you can see the you can have it restore
> to a different name. I don't care for the copy object wizard myself,
> I have probs with it when there are dependencies for ref integrity.
>
> Erik Grob, MCDBA
>
Which version of SQL Server are you using?
I know that when using the Restore Database... option in Management Studio
(2005), you can just change the name of the Database the backup is being
restored to.
For example:
Destination for restore - "To database:" DBname_Test
Source for restore - "From database:" DBname
No need to select "From device:", but remember to select the latest backup
set and transaction logs (if any). Doing this will not affect the production
DB. Of course, this also assumes that a backup of the production database has
been done at some time.
