Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase

Someone just launched BACKUP LOG WITH TRUNCATE_ONLY for his database. Expand / Collapse
Posted Thursday, September 1, 2011 6:50 AM



Group: General Forum Members
Last Login: Tuesday, October 25, 2016 8:37 AM
Points: 6,822, Visits: 8,830
(sql2005EE sp3)
Someone just launched BACKUP LOG WITH TRUNCATE_ONLY for his database.
( I know, I shouldn't have provided dbo auth, but you know how that goes )

Apparently the default trace doesn't record this event :-(

In the instances errorlog file it only states:
BACKUP LOG WITH TRUNCATE_ONLY or WITH NO_LOG is deprecated. The simple recovery model should be used to automatically truncate the transaction log.

[msdb].[dbo].[backupset] Doesn't record this breach

Of course, regular scheduled log backups fail after this event because of the lack of a valid full backup.

For now I've launched a trace to capture "audit backup/restore events", so I'll know the origin by tomorrow

The question is: Where and how could I have discovered / prevented this ?


Don't drive faster than your guardian angel can fly ...
but keeping both feet on the ground won't get you anywhere

- How to post Performance Problems
- How to post data/code to get the best help

- How to prevent a sore throat after hours of presenting ppt ?

"press F1 for solution", "press shift+F1 for urgent solution"

Need a bit of Powershell? How about this

Who am I ? Sometimes this is me but most of the time this is me
Post #1168626
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse