Category
Product Version
Topic
Subtopic
What authentication method does ApexSQL use? (4377107)
When including ApexSQL tools on you environment, it is important to understand the authentication types available. ... <p><img alt="1" src="https://prod-support-images-cfm.s3.amazonaws.com/KB_kA0RP0000002TcD0AU_authenticationapexsql.png"></img></p>
'Auditing filter change monitor' alert information is not displayed in full due to character limitation for the [UserSummary] column in [ApexSQL].[AlertReports] table (4378480)
ApexSQL Audit has a character limitation of 32 000 characters for the text in the UserSummary column from the ApexSQL.AlertReports table. ... When the limit is reached, the text is cut off and ellipsis (...) is placed at the end of the entry both in the UI ( Summary pane of the alert in Alert History) and the UserSummary column in ApexSQL.AlertReports tables (and views).
MaxDegreeOfParallelism error in ApexSQL Audit Logs (4374729)
When adding a server in ApexSQL Audit, after some minutes, the server auditing stops automatically without apparent errors. ... One or more errors occurred. ... Type: System.AggregateException ... Stack trace
ApexSQL Audit - Received Packages building up (4378237)
Events reaching the ApexSQL Audit central repository, thus reports show that there is recent information being captured correctly. ... There is a bug in ApexSQL Audit's mechanism for loading and deleting the packages in this scenario.
Does ApexSQL Audit have the capability to generate reports that monitor and log, when tables are added to, or removed from Before-After configurations? (4378116)
Does the functionality exist in ApexSQL Audit, to create reports that provide visibility into changes made to Before-After configurations? ... Specifically tracking when tables are added or removed?
ApexSQL Audit Server Migration Best Practices (4377701)
This will cause many issue since the database includes embeded encrypted data related to the original server that cannot be changed. ... Creating a new central database on the new server without importing the previous configuration.
Numerous #temp table updates appear in the reports, which haven’t been knowingly created. How can they be excluded? (4377797)
Numerous #temp table updates appear in the reports, which haven’t been knowingly created. ... How can they be excluded? ... If there is a consistent naming convention, a.k.a #temp in this case, please use advanced filters option to exclude it from reports.
The message "Connection to the central instance failed" appears when opening the ApexSQL Audit GUI. (4377497)
When opening ApexSQL Audit the “Connection to the central instance failed” message will appear. ... There can be various reasons why this message appears: ... - The connection between Central and the Domain controller is interrupted
"Error encountered and application needs to be closed" message is encountered when old archives are deleted (4377119)
When trying to delete an accumulated number of archives in the ApexSQL Audit GUI the "Error encountered and application needs to be closed" message is encountered and application crashes WORKAROUND<br>None<br><br>BUG ID<br>234987<br><br>STATUS<br>Waiting for fix in future release of ApexSQL Audit 234987
SQL Parser throws a syntax error for a T-SQL query that contains 'ENSP' HTML space notation (4377058)
The SQL Parser throws a syntax error for any T-SQL query containing the 'ENSP' HTML space notation, resulting in the file being sent to the quarantine folder. ... where(21,1)<br>2024-09-19 14:36:51.852 ERROR [SERVER_NAME\SQL19]: An exception occurred<br>Cannot parse SQL text data<br>Type: ApexSQL.Audit.Processor.Distributed.Trace.TraceException<br>Stack trace<br> at ApexSQL.Audit.Processor.Distributed.Parser.SqlParserHelper.GetParsedObject(String sql, Boolean parseColumns)<br> WORKAROUND:<br>Use SQL Audit technology for auditing instead of Extend events technology or exclude the application/login (ENSP) from the auditing process<br> <br>STATUS:<br>The
ApexSQL Audit main features overview (4216141)
In this article, we are going to quickly look into three main ApexSQL Audit features: ... In order to ensure data safety, easy reporting and being timely and properly alerted on critical events, ApexSQL Audit includes following main features:
"Connecting to central repository. Please wait..." message is showing indefinitely when ApexSQL Audit GUI is launched (4369856)
3) Wait for a half a minute, then launch the ApexSQL Audit again and the connection to the central repository should now be established
ApexSQL Audit performance optimization (4369125)
To ensure ApexSQL Audit Central performance there are some best practices that should be followed. ... Failure to follow these best practices may result in underperformance. ... Ensure that Repository integrity checks not occur during peak hours.
"RESTORE VERIFYONLY" and "RESTORE LABELONLY" are captured as DDL operations (CREATE DATABASE) when using SQL Audit and Extended event data collection (4369285)
RESTORE statements are collected for auditing even when Backup/Restore filter is not selected<br> Expected result: The mentioned RESTORE statements should not be collected for auditing if the Backup/Restore filter is not selected.<br><br>WORKAROUND:<br><br>1.
ApexSQL Audit performance usage - Testing case using Extended Events auditing technology (4369129)
ApexSQL Audit performance usage when using Extended Events auditing technology DISCLAIMER: The following sample represents an insight of resource utilization during overload cases, insinuated with a huge auditing data processing using ApexSQL Audit.
How to activate ApexSQL Audit? (4369441)
ApexSQL Audit is a DBA tool and is licensed per SQL Server instance.<br>This means that each instance requires a license. ... If there are 3 instances, 3 licenses are needed.<br>It's irrelevant whether these 3 instances are on a single physical machine or on three machines.<br>The number of licenses also doesn't depend on virtualization or the number of users.
"Error importing report schedule. Check connection to central instance" message is displayed when trying to import the previously exported report schedule (4369346)
Check connection to central instance" message is displayed when trying to import the previously exported report schedule
A connection issue is encountered when trying to run the ApexSQL Audit API call (4376480)
A connection issue is encountered when trying to run the ApexSQL Audit API call <p>To avoid any kind of connection issues while configuring the ApexSQL Audit API calls it is mandatory that all steps of the below shared articles are completed successfully.<br>If any of those steps are omitted or not completed successfully the connection issues are to be xpected.<br><br>Please check detailed guide into configuring ApexSQL Audit API calls to be used for SQL auditing reports:<br>https://knowledgebase.apexsql.com/using-api-to-generate-sql-auditing-reports/<br><br>To import audit data using Power BI please check the "Importing audit data into Power BI using API call" section of the below guide:<br>https://solutioncenter.apexsql.com/extract-sql-auditing-data-into-power-bi/</p>
Is there a unique identifier field in ApexSQL Audit that links before and after lines, allowing you to join the two together in a report? (4376481)
Is there a unique identifier field in ApexSQL Audit that links before and after lines, allowing you to join the two together in a report? <p>The only unique ApexSQL Audit identifiers we could offer are:</p>
Does ApexSQL Audit have the capability to set alerts when changes are made to reports? (4376059)
Does ApexSQL Audit have the capability to set alerts to notify you when changes are made to reports? <p>This is not currently possible at the moment, but an Enhancement has been created for such functionality in the future.<br><br>WORKAROUND:<br>None.</p>
SQL Parser throws a syntax error during the parsing of an internal query that contains 'OPENROWSET(TABLE' keywords in conjunction (4375777)
SQL Parser throws a syntax error during the parsing of an internal query that contains 'OPENROWSET(TABLE' keywords in conjunction ... In the log files was founded: ... 2024-05-08 12:07:05.622 DEBUG [QDQ6X6Y2]: SQL Parser exited with code 1
SQL Parser throws a syntax error during the parsing of a T-SQL query that contains keyword 'PARTITION' (4375778)
SQL Parser throws a syntax error during the parsing of a T-SQL query that contains keyword 'PARTITION' ... Add a server and a database for auditing using Extended event data collection. ... Run the query below on the audited server:
Alerting has a limit of 10 notifications per minute and subsequently causes extensive memory usage and alert duplication (4375495)
Alerting has a limit of 10 notifications per minute.<br><br>Can the way the application forwards and handles notifications in the background between components be addressed, to remove this constraint?<br><br>When communication between the central and the distributed server continuously interrupts, alerts are not sent to the central server, and memory usage significantly increases.
The date range of reports does not include the entire month or includes days from the previous month when "Last one month" is selected as the period for report generation. (4375054)
Start ApexSQL Audit, add a server and database for auditing using any technology ... Go to Start, find Services and stop the Windows time service (to be able to change the date and time on the VM without issues)
SQL Parser throws a syntax error during the parsing of a T-SQL query "EXECUTE AS USER = SUSER_NAME()" (4375069)
Connect to the audited server in SSMS and make sure that the current user (the user which is currently logged in) is mapped to the database you are auditing. ... In the context of the db that is being audited, run the following command: EXECUTE AS USER = SUSER_NAME();
New Product Association
- Self Service Tools
- Knowledge Base
- Notifications & Alerts
- Product Support
- Software Downloads
- Technical Documentation
- User Forums
- Video Tutorials
- RSS Feed
- Contact Us
- Technical Support
- View All