|
Came back to the office today after being out sick for a couple of days. Our "DBA" (nominally in charge of both our SQL Server and Oracle environments) has decided to enable auditing on the SQL Server because security has been nagging him to do it to address some audit gaps. How did he configure it? Oh he just took all the defaults. So the application log for the host is now wrapping approximately every 20 seconds and retaining zero auditing data. (Our app logs are set to 20Mb and over wrote as needed; we then archive them once a day. This is usually more than adequate.) When this was pointed out to him and using a separate log file suggested, he replied: "To increase the server application log allowing space size or backup event log to a file every 20 seconds or reduce the auditing item are ways to go. To redirect the log to a file has the same disk space issue and we also don't have application to read the file." We're using built in SQL Server auditing which (surprise!) can indeed read its own log files. He also did zero estimation of the necessary disk space to store the 90 days of audit logs he needs to have available... So just dumps everything into the event log so the cjs have to deal with it.
|
#
¿
Aug 19, 2013 17:30
|
|
|
|
| # ¿ May 16, 2024 16:58 |
|