'Truncate log on checkpoint' setting is changing

[jballum]

It seems that at a client site every now and again the tool they are using to perform their daily database backups to tape is failing on some databases. The reason given is that 'Truncate log on checkpoint' is chosen. The client tells me that they then uncheck it and rerun the backup and everything works fine but at some time in the future the same problem pops up.

Is their some way to track someone changing the properties of a database in SQL Server as the client thinks someone is doing this?

Thanks [sig][/sig]

 

[foxdev]

I can't think of any way to log this kind of activity. Seemingly, if they think someone is intentionally doing this, they shoud re-examine their security roles and tighten up on who is granted this permission. [sig]<p>Robert Bradley<br><a href=mailto: > </a><br><a href=

http://www.foxdev.com/>FoxDev

- Visual FoxPro Development</a><br> [/sig]

 

[SQLUser]

Somewhere inside stored procedures/sql scripts/etc... there is code (probably) that says...

sp_dboption 'db_name', trunc. log on chkpt.', 'true'

Check for it!
[sig][/sig]