Hi,
We are using LF 9.
Our DBA team recommended to block all the DBCC commands that LF fires. Mostly on the audit trail database.
If we do it, would there be any loss of functionality in LF?
Thank you
Gian
Hi,
We are using LF 9.
Our DBA team recommended to block all the DBCC commands that LF fires. Mostly on the audit trail database.
If we do it, would there be any loss of functionality in LF?
Thank you
Gian
You're correct, I was looking in the wrong place. AT is supposed to only set that property on database creation but due to a bug it will set it more often. It is fixed in version 10.2.
Recent versions of Audit Trail can be told not to shrink after delete. In the XML file, there should be a line "<Maintenance AutoShrink="true" />". If you change that to false and restart the service it will not run the DBCC shrink command. If you don't do this I think you'll see an entry in the error log when the command fails due to the removed permission.
Thank you for the info Brian,
We are still in v9 and cannot upgrade right now.
Also, there is another command, alter database autoclose that runs a lot.
We can also block the alter database commands. Would this cause an issue?
Ideally we want Laserfiche to not modify the database settings and let the DBAs do it.
Thanks
Gian
Audit Trail does not attempt to change the database's Auto Close settings.
Hi, we are getting lots of this logs in SQL
LogID LogDate ProcessInfo LogText 79 2016-07-27 20:25:52.120 spid115 Setting database option AUTO_CLOSE to OFF for database 'LFAudit_Intertrust-Singapore'. 78 2016-07-27 20:25:51.090 spid115 Setting database option AUTO_CLOSE to OFF for database 'LFAudit_Intertrust-HK_91'. 77 2016-07-27 20:25:49.240 spid112 Setting database option AUTO_CLOSE to OFF for database 'LFAudit_Intertrust-Singapore'. 76 2016-07-27 20:25:43.810 spid115 Setting database option AUTO_CLOSE to OFF for database 'LFAudit_Intertrust-HK_91'. 75 2016-07-27 20:25:42.450 spid112 Setting database option AUTO_CLOSE to OFF for database 'LFAudit_Intertrust-Singapore'. 74 2016-07-27 20:25:37.000 spid115 Setting database option AUTO_CLOSE to OFF for database 'LFAudit_Intertrust-HK_91'. 73 2016-07-27 20:25:35.600 spid112 Setting database option AUTO_CLOSE to OFF for database 'LFAudit_Intertrust-Singapore'. 72 2016-07-27 20:25:30.070 spid115 Setting database option AUTO_CLOSE to OFF for database 'LFAudit_Intertrust-HK_91'.
You're correct, I was looking in the wrong place. AT is supposed to only set that property on database creation but due to a bug it will set it more often. It is fixed in version 10.2.