June 13, 2016 at 11:12 pm
Hi All
I have issue in production server where transaction log in a certain database has less than 20% free space .
I want to do Backup log to disk ‘NUL’ but still worried because database is in mirroring process ( Database is set as PRINCIPAL )
Is it OK to run that script ?
Previously I wanted to change recovery model but it doesn’t work because it is mirroring process
Any feedback is highly appreciated
June 14, 2016 at 12:47 am
It'll break your recovery process and leave you unable to restore to point in time until another full backup is taken. Won't break mirroring, but that may be a small comfort if you end up needing to do that restore.
Why not a normal log backup? You have to be taking regular log backups when the database is in full recovery, so rather let the next normal log backup mark the log as reusable.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 14, 2016 at 7:34 pm
I will do it now , Thanks Gail !
June 22, 2016 at 9:52 pm
So it means it is like changing Recovery model from FULL to SIMPLE because it will break the log backup chain so we can’t do Point in time Recovery ?
June 23, 2016 at 1:46 am
It won't break the log chain, because SQL doesn't know the backup's been discarded, so you will still be able to take log backups, however those log backups will be useless and you'll be unable to restore past the backup that was done to nul, because restoring log backups requires that ALL of them are present and restored in sequence.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply