Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
rx2526
Starting Member
4 Posts |
 Posted - 2012-08-21 : 17:24:17
|
| I have a need to prevent anyone including sa from issuing adhoc backup commands ( native or Litespeed or any other backup command). This is to prevent break in my backup cycle. Any suggestions on using server side triggers, policy management,extended events etc.If this is not possible I would at least want to send a notification that a backup has been completed outside of my regular backup jobs.SQL versions : SQL server 2005 and beyond... |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2012-08-21 : 17:54:24
|
| Not 100% Sure, but you might be able to do something with Policy Based Management (2008+).-Chad |
 |
|
|
jackv
Master Smack Fu Yak Hacker
2179 Posts |
Posted - 2012-08-22 : 01:43:11
|
| Just a thought , but Stopping sa from doing a BACKUP , may be counterproductive in the long run . I can envisage an emergency situation , where this may be necessary. Monitoring the BACKUP history through daily reports may work , or monitoring the SQL Server Logs. Jack Vamvas--------------------http://www.sqlserver-dba.com |
|
|
|
rx2526
Starting Member
4 Posts |
Posted - 2012-08-23 : 19:02:00
|
| I don't mean to stop sa from doing backups. We already have regular backups and all the dBAs do make sure that ‘copy_only’ is used when they do ad-hoc backups. I just want to create an additional safeguard to warn the person who is doing non copy only ad-hoc backup that it can break the diff backup base. |
|
|
|
|
|
|
Prevent non copy_only adhoc backups