Both machines are running SQL2K. I'd like to place the production database
in a directory on the destination machine with a slightly different path
name than the source SQL server.
How can I shrink the transaction log to the minimum size before I try the
move? What is the best way to move the database to the new machine? We
have Veritus Backup Exec.
Regards,
Charles MacLeanPut the database offline, copy the data file/s and the transaction log/s,
and attach the database file from the new path (sp_attach_db).
You can use the command for attaching a single data file recreating a very
small transaction log (sp_attach_single_file_db).
http://support.microsoft.com/kb/224071/EN-US/
Bye
Massimo
"Charles MacLean" <charlesmaclean@.sbcglobal.netha scritto nel messaggio
news:4zAFg.11171$9T3.4998@.newssvr25.news.prodigy.n et...
Quote:
Originally Posted by
I need to move our production database to a brand new machine on our LAN.
Both machines are running SQL2K. I'd like to place the production
database
Quote:
Originally Posted by
in a directory on the destination machine with a slightly different path
name than the source SQL server.
How can I shrink the transaction log to the minimum size before I try the
move? What is the best way to move the database to the new machine? We
have Veritus Backup Exec.
>
Regards,
Charles MacLean
>
>
>
No comments:
Post a Comment