So maybe you downloaded a trial of SQL Compliance Manager and want to play around with it. Or perhaps you already purchased licenses and want to deploy and setup the tool on your SQL Servers. Either way you can always use some help to really configure the product the way you need to fit your specific environment. “The devil is in the details” as they say. Here is a quick resource to help you.
The Best Practices for Deployment of SQL Compliance Manager guide is 5 pages of juicy helpful setting tips and suggestions to consider during configuration of the product.
A few highlights you’ll see in here include:
- Determine what you want to audit – at the database, instance or table level
- Setting up to audit only specific users or privileged users
- Determining auditing requirements for data collection – collect all failed logins, security changes, DDL, DBCC, etc or some variation
- Optimal settings for tempdb and model database for the SQL Compliance Manager repository
- Adjusting configuration settings such as sql statement stored, appropriate intervals to archive data and application permissions and logins
- Best practices for how to roll out to your SQL Servers
- Creating Audit Event Filters
See the full document SQL CM – Best Practices for Deployment as a handy reference to accompany the product documentation.