• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 209
  • Last Modified:

SQL Server Auditing

Currently Running SQL Server 2008R2
I have a few production Databases
I need to set up auditing to track all changes to these servers and all databases on these servers.
For Example Altered Procedures or dropped indexes or changed passwords plus all other major changes
I need to make sure that it is lightweight since I do not want our production environment to suffer. What type of audit can I set up which is not too taxing on the system?
Or will auditing always have a negative impact on the production environment?
1 Solution
Best way is to limit permissions to only a few. Channel the db-changes so they get 'authored' before applied. And so you also can have the possibility to get your db-changes in version control.  You must restore db of last week, no problem and you still have the scripts to do the db-changes which were done since then.

Then you still can 'audit' with DDL-triggers, they don't bother normal usage of your database
See at

Or 'Auditing'
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now