Lee Linares (7/2/2014)
Thanks for taking the time to share this script. I have a question though.
Wouldn't your transaction logs backups that are performed AFTER you shrink the logs and return to FULL recovery model fail unless you first perform another FULL database backup ?
If you try to make a log backup in this situation, I believe the transaction log backup will fail with a "no current database backup" error
My understanding is that when you change from SIMPLE to FULL recovery the database still behaves as if it is still in SIMPLE mode (sometimes called "pseudo-simple") until a full backup is performed.
Shaun Stewart has an article about this problem here:
Paul Randall also has an excellent article this at:
Sorry for the late anwser, but as been a while since i come here.
When your model is in FULL mode you always need a full backup of your database before a TS backup, or else you gonna get an error. After a shrink and returning to FULL yes, fisrt database backup second transaction log backup and the respective log truncate, only the you can make or not a shrink to your log.