IDERA strives to ensure our products provide quality solutions for your SQL Server needs. The following known IDERA SQL Compliance Manager issues are described in this section. If you need further assistance with any issue, please contact Support (www.idera.com/support).
Installation and configuration issues
IDERA Dashboard 3.0.3 and later does not support SQL Server 2005 SP1
Users should not attempt to install SQL Compliance Manager with IDERA Dashboard 3.0.3 and later on a SQL Server 2005 SP1 as that version of SQL Server is not supported by IDERA Dashboard.
Verify SQL Compliance Manager repository database size before upgrading
It is important to check the size of the SQL Compliance Manager repository databases on the Collection Server before proceeding with an upgrade. There are four databases created by SQL Compliance Manager: SQLcompliance; SQLcompliance.Processing; SQLcompliance.<Instance>; SQLcompliance.<Instance>_Time_Partition. Each database should be under 20 GB to complete a successful upgrade. In order to avoid problems during the upgrade due to database size, IDERA recommends that you regularly archive the repository data to maintain the audit history. For more information about archiving, see Manage Audit Data. If archiving the data through SQL Compliance Manager is not an option at the time of the upgrade, it is recommended to back up the repository databases and delete unneeded records from the Events and EventSQL tables of the event databases.
Case-sensitivity required when specifying the Repository database name
When specifying the location and name of your Repository database, SQL Compliance Manager requires that you use proper capitalization.
IDERA SQL Compliance Manager does not capture Linked Server Trace Events for SQL Server 2005
Linked server events are not present in the trace files for SQL Server 2005, therefore linked server events are not captured in IDERA SQL Compliance Manager and no alerts will trigger. Microsoft has ended extended support for this version.
Create/Drop index events recorded as “Alter User Table” event
SQL Compliance Manager records Create/Drop index events as “Alter User Table” events.
IDERA SQL Compliance Manager is not loading events accessed through a View
SQL Compliance Manager does not display Sensitive Column events when accessed from a view. To access the information using views gather and filter out all SELECT statements.
Note that this action will cause extra collection.
SQL Compliance Manager is not able to process alerts when a Group of users is set as a Privileged User
If a group is set as a Privileged User, the triggered alert is not able to detect individual users within a group. To process the alerts, users can set up the alert settings to detect the individual user logins.
SQL Compliance Manager displays incorrect Database name for event type "Create Database"
When users capture a "Create Database" event, SQL Compliance Manager changes the Database name to "Dynamic SQL".
Issues loading BAD auditing information
IDERA SQL Compliance Manager is not able to capture BAD auditing information when two objects with the same name exist in the same schema.
SQL Text is not captured for DDL Statements
When monitoring an instance for DDL event, SQL Compliance Manager is not able to capture SQL Statements for DDL activities unless a user is added to the Privileged User Group. Users can also capture SQL Text by selecting Capture SQL statements for DDL and Security changes at Database Level.
Known issues in version 5.5
General issues
- (Fixed in version 5.5.1) When users try to upgrade from SQL Compliance Manager 4.5 to 5.5, trace files are not processed. If you currently work with SQL Compliance Manager 4.5, before upgrading stop the Collection Service, Agent Service, and disable auditing to stop trace file processing, then proceed to upgrade to SQL Compliance Manager 5.5, and configure and enable auditing. Upon upgrading to SQL Compliance 5.5, users must upgrade all agents to a 5.x version first. For more information, see Upgrade to this build.
| Anchor |
|---|
| SQLCM-5339/5021/5243/5013/5340/5343 |
|---|
| SQLCM-5339/5021/5243/5013/5340/5343 |
|---|
|
(Fixed in version 5.5.1) The SQL Compliance Manager Collection Server is not processing trace files, or processing them slowly, causing backlog files to get accumulated in the Collection Trace Directory in large transactional databases.The workaround for this issue is to increase the tamper detection interval and the Collection interval.
- (Fixed in version 5.5.1) IDERA SQL Compliance Manager installation fails if TLS 1.0 is disabled and if SQL Server 2012 Native Client is not available. IDERA SQL Compliance Manager 5.5 installs SQL Server 2012 native client (version 11.0.2100.60) which does not support TLS 1.2 enabled as per Microsoft.
https://support.microsoft.com/en-us/help/3135244/tls-1-2-support-for-microsoft-sql-server
Users with SQL Server versions prior to SQL Server 2012 R2 SP3 need to enable TLS 1.0 or update the native client to the supported version (11.4.7001.0) following the link below:
https://www.microsoft.com/en-us/download/details.aspx?id=50402
| Anchor |
|---|
| SQLCM-5218/5222/5328 |
|---|
| SQLCM-5218/5222/5328 |
|---|
|
(Fixed in version 5.5.1) SQL Compliance Manager does not process trace files generated by an older Agent after upgrading versions of the Collection Server and the Agent.
Auditing issues
| Anchor |
|---|
| SQLCM-5275/2408/2512/4919 |
|---|
| SQLCM-5275/2408/2512/4919 |
|---|
|
(Fixed in version 5.5.1) When performing an archive of a highly transactional database with SQL Compliance Manager, the application shows a “violation of PRIMARY KEY constraint” error and terminates the statement. The workaround for this issue is to rename the current archive database, along with the database files associated to it and perform a new archive operation. The operation should create a new archive database and database files.
Known issues in version 5.4.x
General issues
- (Fixed in version 5.5.1) SQL Compliance Manager does not accept user names longer than 20 characters and does not support some special characters for the user password, such as £.
- Removing databases using the Administration pane in the Management Console does not work. You can remove databases using the Explorer Activity panel.
- (Fixed in version 5.5) During an Agent-only installation, if you accept the default destination path for SQL Compliance Manager, and then select a different destination drive and use a sub-folder in the Agent Trace Directory dialog box, the installer does not create the Agent Trace Directory during installation. If this issue occurs, reinstall the Agent specifying a folder instead of a sub-folder as the destination path or use the default path specified in the installer.
Auditing issues
- If the audit settings are configured to audit DML events for a selected table, and extended events is enabled for DML and Select on the Instance, SQL Compliance Manager collects audit data for all tables and not only the selected table. If you turn off extended events, auditing correctly collects data for the selected table only.
- (Fixed in version 5.5) Execute events are captured when extended events is enabled. There may be some extra events captured and shown through the Extended Events auditing than the events shown through the Trace method.
- (Fixed in version 5.4.2) Cannot insert duplicate key row in object 'dbo.Events' with unique index 'IX_Events_eventId'.
- (Fixed in version 5.4.2) DatabaseName appears as empty for Login Events. SQL Compliance Manager 5.4 traces do capture the DatabaseID, but do not include the database name.
- (Fixed in version 5.5) Applying a regulation guideline does not work when there is a Privileged User defined.
- (Fixed in version 5.4.2) Case-sensitive collation may prevent some trusted and privileged users from being captured.
- (Fixed in version 5.4.2) Auditing an AlwaysOn database using the Node method causes the Registered SQL Servers list to display both nodes as Secondary.
| Anchor |
|---|
| SQLCM-4205/4718 |
|---|
| SQLCM-4205/4718 |
|---|
|
Audit Snapshot does not include setting to capture DDL SQL statements.- Before-After data does not appear for Binary Collation SQL Server instances when extended events is enabled.
- (Fixed in version 5.4.2) Audit settings at an instance level take precedence over database-level settings for a Privileged User.
- (Fixed in version 5.5) Agent trace folder permissions are overwritten when the Agent is deployed.
- (Fixed in version 5.4) SQL Compliance Manager attempts to contact the Agent (heartbeat check) on attached archive databases.
- (Fixed in version 5.5) Users who export reports to Microsoft Excel fail when the SQL text contains more than 32,767 characters.
- (Fixed in version 5.4.2) Some SQL Server startup/stop events may cause the integrity check to fail.
- The Audit Events tab may display an incorrect user name in the Login column when auditing start and stop server events.
(Fixed in version 5.4.2) A known SQL Server issue causes some SQL Compliance Manager SELECT statements to appear as DML events. This issue occurs when a user audits both SELECT and DML. SQL Compliance Manager captures many events when certain columns are selected from certain system tables from a single SELECT statement query and shows them as individual DML events.
Specifically, the SELECT statement which uses the permissions() function generates only DML event traces and not a SELECT event trace. This step results in SQL Compliance Manager reporting the SELECT statement as a DML event. In addition, the permissions() function is deprecated. Microsoft recommends in MSDN documentation that users implement the Has_Perms_By_Name() function instead of the permissions() function. The difference between these two functions is that the permissions() function always generates the DML event traces while the Has_Perms_By_Name() function generates event traces according to permission type used. For example, SELECT event traces for SELECT permission types, and DML event traces for EXECUTE or DELETE permission types.
- (Fixed in version 5.4.2) Users who change the default port for the AlwaysOn Availability Group from the default may experience the following issues. to avoid these issues, change the listener to the default port.
- SQL Compliance Manager does not accept the name format when attempting to add the listener name using the Cluster Configuration Console.
- If the port is not added, the agent cannot connect to the SQL Server instance. You can manually add the port to the registry setting later and it will then connect to the instance after restarting the SQLcomplianceAgent.
- Users cannot connect to the SQL Server instance even when adding the listener with the port in the SQL CM console.
- The Permissions Check also fails.
When you change the definition of a table you are auditing to include BLOB data types, the Before-After data trigger prevents UPDATE, DELETE, and INSERT operations from modifying the table, such as through stored procedures or third-party applications. This issue is most likely to occur when you are auditing all columns in the target table. This issue occurs because Before-After auditing does not support BLOB data types (such as text, image data, or XML code). To correct this issue, change the data definition of the table.
SQL Compliance Manager does not support collecting and processing events from encrypted SQL Server trace files. This issue is most likely to occur in environments that use third-party encryption software. For example, some applications can be configured to automatically encrypt all new files created on a specific computer. If you are running encryption software in your SQL Server environment, verify the encryption settings to ensure the application does not encrypt trace files on the audited SQL Server instances.
| Anchor |
|---|
| SQLCM-4963/4974 |
|---|
| SQLCM-4963/4974 |
|---|
|
After removing a server from auditing and leave registered databases archived, the user is able to right-click the archived database ‘server’ and register databases to audit. - Users can select “Capture SQL statements for DDL activities” only if the “Database Definition DDL” option is saved first.
Alerting issues
- Filtering by time does not work properly on the Alerts view.
- Some status alerts including Agent trace directory reached size limit and Collection Server trace directory reached size limit do not display properly in the Web Console.
- Status alerts are not generated for alert rules of the Agent cannot connect to audited instance Rule Type.
- (Fixed in version 5.5) SQL Statement is not captured or displayed when viewing Event Properties for Create SQL Login and Create Windows Login events.
- (Fixed in version 5.4.2) A Column Value Changed data alert is generated twice for each Before-After audit event.
Reporting issues
- (Fixed in version 5.4.2) The DML Activity (Before-After) report, when deployed to SQL Server Reporting Services, does not run properly. You can view the report in the Console.