Search SSWUG.ORG:
Welcome to the Pro Center

Show Notes:

A common requirement for database administrators is to be able to track the activity within an instance of SQL. Based on governance, oversight, or policy most organizations require some means of tracking and recording specific events such as:

  1. Failed logins
  2. DDL events
  3. Data access

Ideally the front end application will have a means of capturing these day to day events, but if not SQL provides a number of tools that will audit SQL events and activity. This session will begin outlining the methods, native to SQL, to audit SQL events including:

  1. C2 Auditing
  2. Common Criteria Compliance
  3. SQL Trace
  4. DDL Triggers
  5. DML Triggers
  6. SQL Audit

Each method will be outlined and demonstrated and particular attention will be paid to the resources required for each technique. Much of this session will be spent examining SQL Audit and looking into the internal workings of this technology
Learning Objectives:
Each attendee will leave with the knowledge and toolset necessary to:

  1. Enable C2 auditing
  2. Enable Common Criteria Compliance
  3. Create and configure a client and server side trace
  4. Use DDL/DML triggers to audit activity
  5. Configure SQL audit



Tip: double-click the video to enable full-screen.


comments powered by Disqus


   Topic Area (Click to change):

Related content: