April 23, 2017 at 12:59 pm
Hi,
I;ve been asked to audit few tables, views, stored procedures for some client request and see that it can be done via database audit.
My question is should server audit be enabled before we can get to database audit?
as I got some error message- create failes for databaseauditspec cannot find audit when I tried to setup only database audit?
April 24, 2017 at 1:16 am
Below articles can help you to create required server audit and specifications:
https://tabledependency.codeplex.com/wikipage?title=SqlTableDependency
Alternatively, you may try this automated solution ( https://www.lepide.com/lepideauditor/sql-server-auditing.html ) which can help you to audit required SQL changes from a centralized location.
April 24, 2017 at 1:13 pm
Creating an Audit (server or database) requires two things:
1. An Audit definition at the server level (Server->Security->Audits) which defines *where* the audit will be saved (File, Application Log, or Security Log)
2. A Database Audit Specification that defines *what* is going to be audited, which points to the Audit definition for where to be saved.
If you set the Audit Definition to point to a file location, you need to ensure that the SQL Server service account has Full Control (you could also try lower privileges such as Modify and Read) to the location in question, or SQL won't be able to create the audit files, and the audit fails.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply