Then, restore all the main BAK and all the existing TRN files to the new server but make sure that ALL of those restores, including the last one, ALL use the NORECOVERY option. When you're ready, take a "Tail Log Backup" on the original. That will set the original to "Recovering" status and no one will be able to make any changes. Restore the backup for for the tail log on the new server and use the RECOVERY option. Total down time (for the restore, anyway) will be measured in short minutes if you prepare by making sure that you read up on it and have your scripts ready.
I've done this many times for many databases where I work. We did more than 64 databases of decent size and 1 of them was 2TB and another was 1TB. Total downtime was about 20 minutes.
is pronounced "ree-bar
" and is a "Modenism
" for R
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
"If you think its expensive to hire a professional to do the job, wait until you hire an amateur."--Red Adair
"Change is inevitable... change for the better is not."
When you put the right degree of spin on it, the number 3|8
is also a glyph that describes the nature of a DBAs job. 😉
How to post code problems
Create a Tally Function (fnTally)