Compliance Manager: Auditing Thousands of Similar Databases

I am in the process of running a POC for CM to see if it will fit our needs. We have 60,000 databases - most similar in schema - across 70 or so instances. We also have a separate pool of databases with a different schema that will be monitored slightly differently. The key here is that for both pools we're going to typically only monitor activity on 1-2 tables per database along with security and schema changes on those objects. We also add new databases regularly as well as shuffle databases around instances for load balancing. We need a solution for monitoring that is scalable with this sort of behavior and structure. If we have to touch each database to set this up as well as each time we make a change the tool will be too burdensome to implement. That being said, I have a few questions to those who use Compliance Manager regularly:

  1. Is it possible to create a template for database auditing and apply it to multiple databases at once?
  2. Will the auditing configuration migrate with a database when moved between monitored instances?
  3. Can the audit config be automatically applied to new databases?


- Tim Ford

No Data
  • Hey Tim! 

    We are going to be making some configuration improvements in the SQL Compliance Manager 5.6 release which is due out sometime next year (hopefully in the early part of the year).   In that release you will be able to set up a template and apply it to servers and databases as needed. 

    The current configuration options for Compliance Manager are:

    • Go with the IDERA Default Configurations
    • Apply a Regulatory Guideline that meets your auditing needs
    • Set the configuration at the Server level and not the Database level (which won't work if you just want to monitor some databases and not others)
    • Export  the configuration from one database and then import it and apply it to the databases that you need to 

    I know it won't meet your needs perfectly, but the next release should help significantly. 


No Data