Page History

...

• Anchor
  SQLCM-5539 SQLCM-5539

  (Fixed in version 5.6.1)  Import Database settings with DML/SELECT filters, flips import settings. When users import database audit settings and apply those settings to multiple databases, the imported settings apply only to some databases. If user imports and applies the audit settings to the same databases again, the configuration settings get flipped, applying the import settings to the databases it did not apply to before while deleting the settings from the ones it previously applied them to.

• Anchor
  SQLCM-5514 SQLCM-5514

  (Fixed in version 5.6.1)  Invalid stored procedures call to sp_SQLcompliance_AuditXE. A message about an invalid stored procedure appears in the SQL Server Logs; "Could not find stored procedure master.dbo.sp_SQLcompliance_AuditXE". The error message appears because no stored procedure with the name "master.dob.sp_SQLcompliance_AuditXE" exists. 

• Anchor
  SQLCM-5505 SQLCM-5505

  SQL Compliance Manager Object Activity Report renders all data on a single page. When the Object Activity Report is run, the report displays all the collected data in a single page. 

• Anchor
  SQLCM-5846 SQLCM-5846

  (Fixed in version 5.6.1)  SQL Compliance Manager traces are getting collected on the Passive nodes of an Availability Group. When a primary node becomes a secondary node, the Stored Procedure does not get disabled for the secondary node and the trace files keep gathering. This causes an accumulation of trace files on the secondary node. 

Follow the steps below for the workaround to stop trace files from generating on the secondary node:

1. Launch Trace Manager from the SQL Compliance Manager Desktop Console. SQLCM Menu-bar>Tools>Trace Manager.
2. Enter the SQL Server Instance name and click the Connect button.

   
   

   Note
   When working on a secondary node of an Availability Group, use the secondary´s instance name.

3. In the SQLcompliance Stored Procedures field, make sure to check the “_” and “_” options.
4. Click the “Drop SQLcompliance Stored Procedures” button.
5. In the Registered Traces field, from the list of running traces, select the entries related to the SQL CM traces.

   
   

   Note
   Use the file path to determine the traces related to SQL CM. Or check the Agent Properties for the audited instances to verify the trace directory file path.

6. Once the desired registered trace is selected, click the Stop button. Select the record again and click the Close button.
7. Repeat steps 5 and 6 for the remaining SQL CM traces.

...