December 10, 2020 at 7:15 pm
Taking a tail log is needed in all migration scenarios as it takes the original database offline.
How it is quicker is when you use something like log shipping (or pre stage the database manually with full/diff/logs) to have the new database ready to go. You then take the tail log, copy the file, restore with recovery.
As you already have done a lot of the pre work your only talking a few minutes of downtime.
if your don’t prestage or get the prep work done in that way you have longer downtime.
You have to potentially copy a full backup or take a fresh full backup copy restore etc all the stuff which could be done hours, days, weeks before hand which incurs the extra downtime.
December 11, 2020 at 4:18 am
Hi Expert,
What exactly happens in tail log before the downtime
Shree
December 11, 2020 at 4:22 am
It’s just a normal log backup but with the keyword NO RECOVERY which takes the database into a restoring state so no user connection can happen to it
December 11, 2020 at 6:00 am
This was removed by the editor as SPAM
December 11, 2020 at 6:01 am
This was removed by the editor as SPAM
December 11, 2020 at 6:07 am
This was removed by the editor as SPAM
December 11, 2020 at 6:08 am
This was removed by the editor as SPAM
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply