Tail log backup or use log backup after putting DB into single user mode? I plan to migrate existing SQL Server 2008 DB to new server (has 2017 engine) with minimum down time.  I will do full restore, then log restores (all with norecovery) on the new server up until the time of migration.  I have tested the restore process using my plan which is this:

For the final log backup, my plan now is to set the database into single user mode, then do a "regular" log backup. Do I need to do the "tail" log backup (add NORECOVERY option) while taking this last log backup? if so, then why? If the DB is set into single user mode which means that no one except me can access database, can I omit using NORECOVERY?  I use Ola's scripts to do log backups, and would rather just run my "regular" log backup job after the DB is in single user mode, copy that backup to the new server, and do the final restore.

Bottom line - is there a difference between log backup in single user mode and a tail log backup?
If the DB is set into single user mode which means that no one except me can access database, can I omit using NORECOVERY?


If you are connected to a different database, or when you eventually disconnect any other user can access the SINGLE_USER database.  A Tail Log backup leaves the database in the RESTORING state.  This guarantees that no users can accidentally read or write data to the old database after the cut-over.