ApexSQL Audit Changelog

What's new in ApexSQL Audit 2023.01.2212.0

Jun 19, 2023

Enhancements:
Additional logging is available by activating Debug mode
Additional processing of files from the ActiveSessions folder after encountering 3rd party parsing errors
Creation of zipped files containing details about the queries which could not be processed
Optimization of the Before-after trigger installation process for databases with a large number of Primary Key indexes
Support for hosting the Central Repository and auditing events for SQL Server 2022
Fixes:
2219140: API JSON output adds comma characters at the end when 'eventsPerPage' value from the URL is greater than 50,000.
220351: API call link cannot be opened in the browser (or used to generate data in power BI) when logged in as a user different to the one running ApexSQL Audit central.
221921: DML operations inside of a stored procedure are not audited when using Extended event data collection.
222518: The auditing configuration is not applied due to timeout being strictly defined as a 10-second value that is now set to follow global timeout settings.
222602: Application log messages are incorrectly labelled as INFO instead of ERROR when an error occurs while creating audit sessions.
222847: Package is not quarantined when a SQL Query operation type is not extracted correctly from query text data in a specific case.
223536: Cannot parse "Deny a permission to principal" operation when there are blank spaces at the end.
224205: An Extended event session file containing auditing data gets deleted by SQL Server when a very large number of operations is being executed
221223: 'Saving configuration was not successful' message is displayed when trying to exclude a local login in a domain environment
225537: SQL Audit auditing configuration is only partially applied when a database which doesn't exist anymore is included in the configuration filters
225485: Auditing configuration is only partially applied when there is an ApexSQL Audit Extended event session on SQL Server in stopped state
227648: ‘Saving configuration was not successful’ error is encountered when applying a Before-after configuration for an Availability Group
227647: ‘Error connecting to server’ is encountered when trying to add a database after an Availability group has been added for auditing
227557: Error ‘Msg 10314, Level 16, State 11’ is encountered when trying to update a table on the (new) primary AG replica after a failover
227466: SQL Audit database session is not properly created after a failover occurs in an Availability Group
228349: An Availability Group cannot be added via listener name if the FQDN of the listener is used
227237: AG cluster cannot be added via listener name if the name doesn't match the one given to the Availability Group
228615: Incomplete data after reading Microsoft Extended Event file using the MS function - fn_xe_file_target_read_file
228776: Auditing sessions are not properly created when a specific combination of filters is used
228590: The Before-after section of the UI is not responsive when adding a database with a large number of Primary Key indexes.
219710: 'Saving configuration was not successful' is displayed when trying to apply a Before-after configuration with a large number of tables and columns
229130: Tables are not successfully loaded in the Before-after configuration when adding a database with specific case-sensitive collation settings
229547: 'MERGE INTO' operation is captured as 4 events when using SQL Audit data collection
229583: 'DBCC CHECKDB' command is captured with a duplicate record when using SQL Audit data collection
229666: Continuous connection timeouts occur because the max pool size has been reached
229601: Extended event and SQL Audit sessions are improperly filtered on the SQL instance for all databases except the first one from ApexSQL Audit's configuration filters
229777: Auditing agent processes for Always On and FCI clusters are not successfully updated after an upgrade to a new version
229779: SQL Audit and Extended event sessions are not properly created when system databases are added for auditing
Changes:
The column order of Before-after reports has been modified and is now displayed in alphabetical order. This modification enables a significant performance improvement both during the initial setup and when updating the configuration for Before-after auditing.

New in ApexSQL Audit 2021.01.2093 (Jul 22, 2022)

New in ApexSQL Audit 2021.01.2091 (Jun 22, 2022)

New in ApexSQL Audit 2021.01.2089 (Jun 1, 2022)

New in ApexSQL Audit 2021.01.2085 Patch (Feb 10, 2022)

New in ApexSQL Audit 2021.01.2082 (Dec 16, 2021)

Enhancements:
Reconstruct raw audit data using web API calls
Repository maintenance schedule to optimize performances while viewing and managing audit data
Report preview and export performance increased up to 900%
Interactive search option for the report filters
Fixes:
188361: Sensitive columns are not audited when a SELECT statement does not include a schema name reference
209651: Active traces pile up on the file system when queries with 5k+ characters in length are being processed in parallel by the auditing agent
208782: Saving audit configuration is not successful when the logins filter contains SQL Server login accounts
208572: Saving audit configuration is not successful when using advanced filters and the login filter is defined to contain custom string
209440: Trace files being accumulated due to internal thread-race error in specific case
208170: Improved application logging to include more granular information for auditing agent startup events
197755: SQL Server event is not captured when the login account creating the event is member of a nested Active Directory group
201647: SQL Server event is not captured when the login account creating the event is newly added to an audited Active Directory group
201648: Extended event session configuration changes audited logins list to an Active Directory group name when the central Server Side Components service is restarted
202867: "The specified database size limit is greater than the size of data source" message is shown in the database split summary when the process exceeds 30 seconds timeout
203615: Auditing agent does not automatically establish connection with auditing SQL Server instance when logon server is unavailable at machine start-up
203616: Timeout value in agent auditing properties dialog is not applied as a running timeout when the agent is reading audit data from session files
200269: Auditing filter configuration is not applied when total character size of filter conditions exceeds 3000 characters
200270: Auditing data is not collected when the text data filter condition is used with advanced filters via extended events
198238: "Destination array was not long enough. Check destIndex and length, and the array's lower bounds." error is encountered with parser and trace files cannot be processed when a specific query with brackets and aliases runs on a SQL Server
196929: Trace files are moved to quarantine when more than 10.000 unique audited queries are executed in a batch
194590: Missing parent checkbox to select all instances in the Apply to many dialogue for SQL server audit configuration
203622: Automatic auditing template in the Options window can be changed by a user with the reader role when the filter item label is clicked
213886: Application is forcibly closed when an imported custom data alert containing email recipients is selected with the mouse click
214026: Alert history shows no alert notifications when time-range filter is used
214025: Data collecting agent does not release occupied RAM memory when processing highly transactional SQL Server instances
206164: Auditing reports show Success status for executed queries that failed on SQL Server when Extended Events data collection method is used
209052: Report filters and output show duplicated server name when SQL Instance is configured via FQDN and is audited using Extended Event technology
208154: Login filters are not applied on auditing configuration when gMSA is used for central process
105045: Missing column statistics events do not contain text data details when shown in generated reports
210403: "invalid token for impersonation - it cannot be duplicated" error is encountered in the Central instance configuration installation process when the application losses and re-establishes connection to central host during the process
210536: Central instance initialization process lasts extensively long after archiving when alerts history contains more than 50K records
210128: Using shift+click action does not select multiple items
155936: Send logs does not collect the re-rolled (archive) log files from the file system
214369: Automatic databases auditing configuration is not applied against SQL Server instances configured to includeexclude specific logins
161967: Access list items are placed in separate cells when a report is exported into CSV format
163664: Alert rule configuration does not have “state” condition available in the alert configuration wizard
164289: The ENABLE TRIGGER statement is shown as the Alter trigger operation in generated reports
164290: The DISABLE TRIGGER statement is shown as the Alter trigger operation in generated reports
165141: Selected tables will be deselected in the Before-after configuration tab when the search is used in the table list
165173: Duplicate alert will be created when importing system alert rules from exported xml
167875: “Accessing from local not possible” message is shown without enough information when Browse for folder is initiated for the remote agent configuration
179533: Missing information for failed archiving when an existing archive used as data source cannot be opened
182294: Text data does not show object name for the SELECT statement in the export document when the object is placed within brackets ("[]")
190967: The “Row type” field is randomly formatted in exported file for Before-After events
191557: Scheduled report fails to complete when archiving is started at the same time
191885: Application stops responding when group checkbox is used for the column listing in the sensitive column view
191897: "Username and password are incorrect or provided user permissions are insufficient" message is shown when gMSA account for remote auditing agent is updated
192379: The Additional drop-down menu in the Configure tab remains active when the Advanced filters are selected and popup message is shown
192389: The SELECT INTO statement is captured as Alter schema operation when run on SQL 2012
194326: The “State” filter item is not shown in generated report header when used
214505: Internal event log showing that a session file is sent to quarantine do not include the time details
214878: Missing information in application logs about text data parsing errors
198777: The CREATE SEQUENCE statement is not being audited when the Trace technology is used
199042: Extended Event sessions are not created when audited database contains brackets in the name ("[]")
200149: Sensitive column access event is not audited when sensitive columns are queried using column concatenation
202224: Database files for central repository database are not moved to new location when the option to archive old database is used in the central instance configuration dialogue
202562: Object names are duplicated in the reporting filters when object reference in query text data uses different letter capitalization
204005: SOX compliance standard does not include Backup/Restore Server-level operations
204908: Unused allocated space is not released when archiving process is finished
205330: Database auditing filters are not correctly applied when configuring the auditing policy for database objects and the objects are grouped by schema and type
214368: The refresh status instead of stopped status icon is displayed in the server tree for SQL Servers when GUI is restarted after stopping the auditing for that instance
161718: The “Trial period expired” message is not removed when the product is activated
164632: “The internal error -2” message is shown when the drive root path is chosen to create a temporary files location on
178153: The CREATE TABLE statement is captured and shown in reports twice when Extended Events technology is used and the table name string contains a T-SQL reserved word
192382: The report exported in XLSX format exceeds page size width when opened with Excel
192385: The Before-After filter conditions are duplicated in advanced filters when the view is switched to another tab and switched back to the Before-After tab
192390: The CREATE TABLE statement is captured as Alter schema operation when run on SQL 2012
201368: The text data with single line size is not visible in records shown when the report preview is generated
203936: Send log process cannot be completed when the message that an audited server is unreachable pops up
207709: The hostname from which a user changed Auditing filters is missing in the configuration change even when the internal report is generated
213238: Missing indicator for the parent check box that some child items are selected in the “Apply to many” databases dialogue when the pre-checked database exists in the child item list
Changes:
The default value for SQL text data length is set to 512 characters

New in ApexSQL Audit 2020.04.2061 Patch (Aug 25, 2021)

New in ApexSQL Audit 2020.04.2060 Patch (Aug 6, 2021)

New in ApexSQL Audit 2020.04.2057 Patch (Jun 24, 2021)

New in ApexSQL Audit 2020.04.2056 Patch (Jun 14, 2021)

New in ApexSQL Audit 2020.04.2054 Patch (May 17, 2021)

New in ApexSQL Audit 2020.04.2052 Patch (Apr 15, 2021)

New in ApexSQL Audit 2020.04.2050 Patch (Mar 4, 2021)

New in ApexSQL Audit 2020.04.2045 Patch (Jan 19, 2021)

New in ApexSQL Audit 2020.04.2038 (Nov 6, 2020)

Enhancements:
Added configuration settings for extended sessions for auditing data collection management
Detailed report metadata is now available in the report header in the export file
Apply auditing configuration to multiple SQL Server instances and databases
Fixes:
178163: The Drop trigger event is shown twice in reports when using the Extended Events data collection method
182827: The Create trigger event is shown twice in reports when using the Trace data collection method
182828: The Alter trigger event is shown twice in reports when using the Trace data collection method
182829: The Drop trigger event is shown twice in reports when using the Trace data collection method
183534: Additional storage space is consumed during upgrade installation when structural changes are introduced into central repository database
186429: “Empty name is not legal” error is encountered, and application closes when the field for report name is left empty
186430: The e-mail recipient list is not shown in the summary info of the schedule archiving wizard
187123: The SQL Server connectivity monitor system alert performs SQL connection checks to the passive node in fail-over cluster environment
187166: The path for the central repository database file in the central instance setup dialogue always reverts to default when custom path is chosen
188362: Advanced filters for before-after auditing are not saved when landing to another tab immediately after applying configuration
188363: Sensitive column list in the configuration tab cannot be refreshed for the selected database when GUI is restarted
189137: Several filter parameters for generating reports are not saved in created profiles
189313: “Index was out of range. Must be non-negative and less than the size of the collection” error is encountered, and application closes when any schema is checked in the Include/Exclude database object view and the Group by schema and type option is turned ON
189314: Sensitive column search fails due to encountered timeout for databases with long queried views
187256: The date settings dialogue controls for the Date filter item is not visible in reporting Advanced filters when screen resolution is set to 4K
190569: Incorrect render of "new line" input for the SQL text query data in the report export
191554: The defined value for Text data filter item is not visible in advanced filters configuration
192447 The report export is not attached with the e-mail notification for scheduled reports when there are no events captured
Changes:
The schedsule wizard now prompts for confirmation when closed before configuring
The title bar for the application GUI title now includes the information about account that is running the GUI
The database maintenance internal event report now shows filters used for archive data purging
Databases in the Apply profile dialogue are now grouped per hosted server instance
Sensitive columns list in the Sensitive data access alert configuration wizard now indicates SQL instance affiliation

New in ApexSQL Audit 2020.03.2021 (Aug 17, 2020)

New in ApexSQL Audit 2020.02.1708 (Jun 11, 2020)

New in ApexSQL Audit 2020.01.1705 (Apr 29, 2020)

Fixes:
Duplicate events are shown in the auditing report in specific case
The 'Auditing stopped' internal event is not audited
Schema and Object name are not audited for Bulk insert operation
Schema and Object name are not audited for Create table insert operation
Configuration changes are not applied when database objects are filtered with include/exclude in simple filters when SQL Audit auditing mechanism is used
Auditing mechanism info is not shown in the status overview tab
Internal events are not affected by the server filter
Changes to the "Attach report to e-mail in .zip format" are not saved
Extended events technology is not auditing SQL Statements forwarded form "exec sp_executesql @statement"
The 'contains' filter criteria will not properly filter events if used in conjunction with "Login name" filter type
The "Network connectivity" alert does not raise notification in a specific case
DML operations are not audited in case when two compliance templates are merged
The "Make new folder" button is not working when creating a location for Schedule Report output
SQL text data is truncated when Create/Alter server trigger events are audited via Extended Events
SQL text data is truncated when login failed events are audited via Extended Events
Create/Drop login events are logged twice when audited via Extended Events
Create table operations are logged twice when audited via Extended Events
Alter service master key SQL statement is logged twice when audited via Extended Events
Object name column is empty for close symmetric key SQL operation
EXEC SQL statement is not audited via Extended Events
Alter queue SQL statement is not audited via Extended Events or Traces auditing mechanisms
Configuration cannot be applied when group by schema and type filter is used via Extended events or SQL Audit mechanisms
Application is closed if the 'unknown' filter is used for client host
Importing auditing configuration fails when Extended Events or SQL Audit auditing mechanisms are used
Enable and Disable trigger operations are incorrectly logged as Alter trigger operation when using Extended Events
Auditing configuration deployment fails due to NULL reference exception when SQL Server is renamed
Enhancements:
Configuration change system alert has been added
Report exporting is up to 200% faster for all supported report formats

New in ApexSQL Audit 2019.04.1654 (Apr 2, 2020)

New in ApexSQL Audit 2019.03.1640 (Nov 25, 2019)

New in ApexSQL Audit 2019.02.1638 (Nov 19, 2019)

New in ApexSQL Audit 2019.01.1635 (Oct 7, 2019)

Enhancements:
Extended Events can now be used as an auditing mechanism for SQL Server 2012 or higher
SQL Audit can now be used as an auditing mechanism for SQL Server 2017 or higher
Up to 200% smaller overhead when using SQL Auditing or Extended Events auditing technologies
Up to 200% faster processing of audited data when using SQL Auditing or Extended Events auditing technologies
SQL Text data is now customizable in auditing configuration on both server and database levels
Dynamic date/time filters are now available in advanced filters as well
MDF file location can now be customized in the Central Repository installer
Fixes:
End of installation process will needlessly prompt Windows restart
Report summary icons are not showing proper objects
Report summary is missing information of the applied compliance standard
System databases are not distinctively shown in browse database dialogs
“No such host is known” message is shown when user initiates the send logs from GUI that is not connected to the central
x86 SQL Server instances are not listed in the repository installer drop-menu
"Group by" checkbox remains checked after ungroup is chosen in the report/schedule history
Control buttons are missing in grid view header in Archiving history
Operation overview status check enters infinite loop and affects GUI performance if there are no events on the selected SQL Server instance
Central repository database is listed in the maintenance wizard controls
Administrator credentials are not saved upon expanding the Advanced options in the Auditing agent properties dialog
Account validation of remote GUI fails in case where Domain Controller machine does not share the same version of .NET runtime environment with the Central
There is no control for MDF file configuration in the Central Repository installer
Operation state is shown as “Failure” in case when "IN (x,y)" condition is used in SQL Query
Loading packages from 2016 to 2018 product version fails
Excluded database objects with similar name to included objects are shown in the reports
"Trial period has ended" message is shown in the Status tab when the central machine is rebooted or when the application is updated, even though it was activated previously
“Archiving failed” error is encountered when report scheduler that was used to generate report is deleted and full report schedule history still exists
“Network connectivity monitor” built-in alert notifications are not being triggered when network connection with auditing instance is lost
Archiving old database during the installation process fails in specific case
Fixing server connection process crashes application in specific case
ApexSQL Audit GUI will use all available CPU resources while refreshing the status without waiting for the ongoing refresh status process to complete
The “Create login operation” state is always shown as “successful”
DBCC operation is collected twice for same transaction in auditing trail
Create/Drop statistics are incorrectly recognized as Alter table operation
Save button is generating a report preview when list of columns is changed
Operation "Drop sequence" is not being audited
Operation "Create sequence" is not being audited
The latest updated version is not stored in archive if upgrade process fails but has made an update on any newer version
Global info is not updated in the status bar after product activation
Default HIPAA and Basel II reporting templates ignores the time range filter configuration
Default HIPAA and Basel II reporting templates always switch to advanced filter type when time-range is not set to "All days"
Pre-defined reporting templates do not take custom time filter into account
Archiving history list is using single page
Internal events are not listed in the internal event type
Weekly schedule always executes on Sundays
Link for testing e-mail configuration is not presented as a hyperlink in 4k resolution

New in ApexSQL Audit 2019.01.1635 (Oct 7, 2019)

Enhancements:
Extended Events can now be used as an auditing mechanism for SQL Server 2012 or higher
SQL Audit can now be used as an auditing mechanism for SQL Server 2017 or higher
Up to 200% smaller overhead when using SQL Auditing or Extended Events auditing technologies
Up to 200% faster processing of audited data when using SQL Auditing or Extended Events auditing technologies
SQL Text data is now customizable in auditing configuration on both server and database levels
Dynamic date/time filters are now available in advanced filters as well
MDF file location can now be customized in the Central Repository installer
Fixes:
End of installation process will needlessly prompt Windows restart
Report summary icons are not showing proper objects
Report summary is missing information of the applied compliance standard
System databases are not distinctively shown in browse database dialogs
“No such host is known” message is shown when user initiates the send logs from GUI that is not connected to the central
x86 SQL Server instances are not listed in the repository installer drop-menu
"Group by" checkbox remains checked after ungroup is chosen in the report/schedule history
Control buttons are missing in grid view header in Archiving history
Operation overview status check enters infinite loop and affects GUI performance if there are no events on the selected SQL Server instance
Central repository database is listed in the maintenance wizard controls
Administrator credentials are not saved upon expanding the Advanced options in the Auditing agent properties dialog
Account validation of remote GUI fails in case where Domain Controller machine does not share the same version of .NET runtime environment with the Central
There is no control for MDF file configuration in the Central Repository installer
Operation state is shown as “Failure” in case when "IN (x,y)" condition is used in SQL Query
Loading packages from 2016 to 2018 product version fails
Excluded database objects with similar name to included objects are shown in the reports
"Trial period has ended" message is shown in the Status tab when the central machine is rebooted or when the application is updated, even though it was activated previously
“Archiving failed” error is encountered when report scheduler that was used to generate report is deleted and full report schedule history still exists
“Network connectivity monitor” built-in alert notifications are not being triggered when network connection with auditing instance is lost
Archiving old database during the installation process fails in specific case
Fixing server connection process crashes application in specific case
ApexSQL Audit GUI will use all available CPU resources while refreshing the status without waiting for the ongoing refresh status process to complete
The “Create login operation” state is always shown as “successful”
DBCC operation is collected twice for same transaction in auditing trail
Create/Drop statistics are incorrectly recognized as Alter table operation
Save button is generating a report preview when list of columns is changed
Operation "Drop sequence" is not being audited
Operation "Create sequence" is not being audited
The latest updated version is not stored in archive if upgrade process fails but has made an update on any newer version
Global info is not updated in the status bar after product activation
Default HIPAA and Basel II reporting templates ignores the time range filter configuration
Default HIPAA and Basel II reporting templates always switch to advanced filter type when time-range is not set to "All days"
Pre-defined reporting templates do not take custom time filter into account
Archiving history list is using single page
Internal events are not listed in the internal event type
Weekly schedule always executes on Sundays
Link for testing e-mail configuration is not presented as a hyperlink in 4k resolution

New in ApexSQL Audit 2018.09.1618 (Jun 21, 2019)

New in ApexSQL Audit 2018.09.1612 (May 9, 2019)

Enhancements:
Repository archiving can now be scheduled
Purge data from specific time range
Split repository archives to multiple databases based on time and/or size
Large reports are now automatically split into multiple files
Scheduled report email information and details can now be customized
Historical overview and details of scheduled report jobs are now available
Fixes:
The Make new folder button is missing in the Browse for folder dialog during the installation
Installation folder must be provided even if the previous tool version is detected and the upgrade process is initiated
Saving report changes fails when only Internal events are included in the report
Warning message is shown repeatedly when configuring alert conditions in case when any SQL Server instance is not connectable
Information in the test summary for Cc and Bcc fields will overlap each other if multiple entries are added to the To, Cc, Bcc fields
Total operations counter does not count in before-after events
“Updating before-After configuration failed” error is encountered when updating before-after configuration on Windows Server 2019
The application does not block adding the unsupported SQL Server versions to be configured for auditing with a misleading result due to the inability of starting such configurations
Alerts are not being triggered for databases that belong to an availability group
Before-after column filter does not filter out records for the tables that share the same column name with the tables that are filtered in
The application closes when the value for "on day" reporting schedule settings is set to value greater than 31
Search/find alerts will not include results which include appropriate value in the alert description
Only “equal or greater than” operator is available in the SQL Script based alert condition
"Folder browsing in remote client not supported. Write directory path from central instance manually" error is encountered when trying to browse for folder during the manual archiving wizard using remote client
The Object type “table” is not available in the advanced filter configuration
Remote SQL Server instances can be targeted when installing the Central Repository Database
"An error occurred while processing request on central instance" error is encountered when generating excel reports which reach Excel 65.000 rows limitation
If scheduled reports are empty they still get send to configured email recipients
Email reports are always zipped
Before-after auditing will show auditing values even in cases when execution of DML operations ended unsuccessfully in High Availability AlwaysOn environment
It is not possible to copy/paste a login name when adding user
Apply button is missing in the E-mail recipient list
Reports are not showing data when state success/failure filters are used for internal events
The "Add table" ribbon is not shown when server is highlighted in the server tree
Alerts with the same name can be added using import/export alert
Importing Advanced filter configuration fails in case when there is no previous configuration on the specific SQL Server instance
“Object reference not set to an instance of an object” error is encountered when refreshing 'Add server' form
Remote client users are not informed that the archiving process is in progress
Two consecutive information messages are shown if archiving process fails
Browse for folder dialog is not affected with theme selection
Named failover cluster instances (FCI) are incorrectly recognized as passive
It is not possible to copy/paste a password field in the agent auditing properties
Exclude filter on database object does not exclude stored procedures
“Package loading failed” error is encountered when updating application from version 2016 to 2018
Scheduled report is not triggered on time after central instance converts to summer/winter time
Multiple schedule executions are shown if the schedule includes multiple output formats
Schedule log is missing info/column on execution success/fail and execution time
Before-after auditing will not capture events when FIPS Windows feature is enabled
Fixed permissions are not inherited for the users inside the defined AD group
Fixed application mode (Administrator) is automatically assigned for the DC admins
Archiving process info messages are not affected with theme selection
Going back through the schedule wizard will show email config even if email send is disabled
Application crashed in case of a backtrack from the second step to the first step in the schedule wizard
Status overview does not retrieve data information for SQL Cluster instances
Last operation in status overview displays IP address instead of SQL Server name for SQL Cluster instances
Report schedule history is not refreshed after scheduled job is executed
Application crashes with unhandled exception when switching from simple to advance filter type while an operation state is defined in simple filter
"An error occurred while processing request on central instance" error is encountered when exporting before-after events to CSV format
No data is shown in the before-after report if the "Object name is not xyz" condition is used
Tampering with Schedule and ArchiveSchedule tables will not trigger integrity breach
Changes:
The application now requires Microsoft .NET Framework 4.7.2
Central repository now initially requires 1GB diskspace (down from 5GB)

New in ApexSQL Audit 2018.08.1535 (Feb 6, 2019)

Enhancements:
A warning is now displayed in case when connection with an incompatible UI version to the central instance is initiated
Package data is now encrypted
Fixes:
"No events found" report results are shown if before/after value filter is used while pulling data from archive
Table and column names are invisible in the before-after column filter in the reports
"An error occurred while processing request on central instance" error is encountered when generating reports with large number of events
CRD becomes unresponsive when multi GUI instances are running on the same machine and archiving is initiated
Server and database objects are not displayed in advanced configuration filter when configuring Failover cluster instances
Server and database objects are not displayed in advanced before-after configuration filter for Failover cluster instances
Server list does not show audited SQL Server instances and databases if an audited database is not accessible
Alerts history list is cleared if refresh or navigation buttons are used
“Problem occurred on central instance” alert remains active in the status tab in case of database inactivity even after the triggered alert has been deleted
Stopping the report exporting or preview generation processes incorrectly informs user that archiving process is in progress
Incorrect number of alerts is shown when alerts are filtered by severity level
Only first compliance configuration template is applied in case multiple compliance templates are used to overwrite existing configuration without applying templates in-between
Retrieving auditing agent data does not retrieve previous information about client hostname when server is being edited
Temporary files location does not point to the last configured location in the agent auditing properties window
“Central repository inactivity” alert is shown as active even after the alert has been resolved
Create/Alter trigger operations are not being audited
"Saving configuration was not successful" error is encountered when adding specific tables for before-after auditing
Expanding/collapsing tree view in the reports tab will trigger a configuration change and prompt to save/discard
Application does not inform user on incorrect time-date filter setup if start time is greater than the end time in the reports
Traces including before-after audited data are not being processed in case that they include special characters in the name like: “-“, “,” etc.
"Error adding database(s)" error is encountered when adding databases for auditing in case a SQL Server instance which does not host chosen databases is selected in the server tree
Server list does not show audited SQL Server instances and databases in case a table added for before-after auditing is renamed
Server list does not show audited SQL Server instances and databases in case an audited database is deleted from SQL Server instance
"Preview unsuccessful" is encountered when using more than 5 filters in the report when generating report preview
A link to the output folder is missing in the schedule summary
Application UI freezes and indefinitely remains in responding state when trying to disable a running schedule
Empty reports are generated in case when archived repository which is included in the data sources list is removed from the SQL Server instance
Imported system alerts cannot be deleted

New in ApexSQL Audit 2018.07.1511 (Nov 7, 2018)

New in ApexSQL Audit 2018.06.1506 (Sep 27, 2018)

Enhancements:
New error handling and send logs functionality
Improved application installer with a dark theme
New application icon
Various filters based on alert details have been added to the alerts history pane
Alerts can now be copied and exported
Server-side components on remote instances are now automatically uninstalled when main application uninstall performed
The SQL script can now be directly tested within the alert wizard
Filter ‘by state’ has been added to the report preview
Triggered alerts can now be marked as resolved
The Primary key column value is now included in the auditing reports when auditing before-after values
Before-after events can now be filtered by column in the report preview
Before-after events can now be filtered by before-value and after-value in the report preview
Bulk-inserts can now be audited for before-after values
Fixes:
Application crashes when accessing schedules if there is an existing expired schedule
In case when several SELECT operations are executed and audited consecutively, they get merged into one audited event which is then repeated 3 times
ALTER database operation is reported as successful even if the execution has failed
Certificate related operations are not audited
Server-level DROP operations state is presented as N/A even in cases when operations have been successfully executed
Server selection changes to the first server in the list when switching to the advanced filter
Application fails to display notification that server-side components cannot be installed directly to an FCI node via Add server functionality
The 'SQL Server connectivity monitor’ alert is incorrectly raised during the repository archiving process
The ‘Disk space’ information is shown as N/A in cases when a disk drive is located on a remote network machine
Time input for the Scheduler reverts to the default value if custom date is used
The ‘Internal error -2’ error is encountered if temporary folder location finishes with the ‘’ symbol
Before-after triggers can’t be applied when there is already an existing database trigger with defined ‘last’ property
The ‘At least one action must be selected’ warning message is displayed when creating a new schedule in case when no other schedules are active
The tooltip in the Auditing agent properties dialog does not match the dark theme
Several elements are overlapping in the configuration pane in 4k resolution
Before-after auditing doesn't successfully audit the data when nested CLR triggers exist in cross-referenced tables
The before-after triggers are not removed on application uninstall in a specific case
The ‘There is already an object named 'Accounts#Const' in the database’ error is encountered when upgrading from 2107 to 2018 version in a specific case
Audited event is not captured in case a SQL View from non-audited database executes SELECT on an audited database
The EXEC events are not audited
The ‘Provided user name is not recognized as a Windows user or user group’ error is encountered when adding user accounts in case when central repository host name has been changed
The "Object reference not set to an instance of an object" error is encountered when adding entries to the email recipient list in a specific case
The email recipient list for an existing alert is not updated when the change is executed via Options dialog
Saving changes in a report template collapses previously expanded level tree view
Default template is incorrectly selected after changes are saved on a custom report template
Previously added local user account is recognized as a domain account in a specific case
Changes are not remembered for the edited mail recipient in case when only existing information is updated, and no new information is added to the existing recipients
Changes in the options dialog are rolled back if user switches to another tab in the options
User is not informed if different application version is being used when connecting via remote GUI
SQL text is being truncated in the report preview in specific cases
Status overview does not change the state in case when auditing instance connection is severed
GUI freezes when updating the configuration for the unresponsive auditing instances
The alert counter inside the status bar is not following the current history active alerts
Application does not notify the user if server-side components are not installed on the cluster node when adding active/passive server for auditing
Changes:
The 'System' alerts can no longer be deleted
The ‘ApexSQLAuditBeforeAfter’ temporary database is no longer used to temporarily store before-after audited data
A separate SQL trace is now used for each database audited for before-after changes
Database triggers created for the purpose of before-after auditing no longer require ‘first’ or ‘last’ triggering property

New in ApexSQL Audit 2018.05.1444 (Jul 23, 2018)

Enhancements:
The server-side components can now be automatically installed from within the application GUI when adding SQL Server instances in the domain environment
The “Inactive repository” alert has been added as a new system alert to notify users if no auditing information has been added to the central repository period for a designated period
Fixes:
The "String or binary data would be truncated" error is encountered when audited batch insert has more than 8000 characters
Adding a new SQL Server to the before-after configuration via remote client fails in a specific case
The State column is missing in the Schedules panel
The “Insufficient privileges” warning message is shown when adding a database for the before-after auditing even though user has administrative privileges in a specific case
Auditing configuration information is not shown when navigating from the Status tab to the Configure tab
Part of the batch inserts information is cut-off in the report preview
Missing information message that the creation of before-after triggers has failed
Adding servers in the AlwaysOn environment fails when non-default port is used by the listener
Missing information on the affected SQL Server instance in the Last operation details in application overview
The "Failed to remove database" error is encountered if database is removed from the before-after auditing in case an auditing configuration has not been previously applied
Server-side components are not installed on all nodes and replicas when adding clustered servers for auditing
The “Central repository inactivity” alert remains active even after the issue has been resolved
The application gets unresponsive when there is a delay while loading the reports
The number of active alerts in the ribbon always shows zero active alerts
The "Username and password are incorrect" error is encountered when upgrading to a new version with credentials previously saved by the application
Missing information on checked objects is missing in the summary, if all objects are manually included
The “SQL Server connectivity monitor” alert is triggering for the passive node in the cluster
The Browse for folder button is missing in the Servers properties form
The Cancel button is missing in the Generating preview pop-up form
Checkboxes are missing on the group level when objects are grouped in the object filter
The central repository database is not checked by default in the verify integrity check
The Alert history grid is missing headers
The CTRL+C and CTRL+V shortcuts are not working in text fields in the Email recipient list form
The Update statistics operation is incorrectly displayed as alter table operation in the reports
The “Server was not added for auditing” error is encountered when servers belonging to the cluster is added for auditing in case when server ping is disabled in the network/domain
The “Object reference not set to an instance of an object” error is encountered when applying compliance filter to the specific set of databases
The Alert history grid is not groupable by columns
The before-after values for the very first operation are not included in the exported report
The Schedules panel is missing a header for the grid
Server-level status overview is missing the Operation overview info for the selected SQL Server instance
The Alert history grid does not include alert name column
The "Error stopping server" message is shown when trying to stop server when connection to the server is severed
The schedule summary is not shown in the final step of the schedule creation wizard
Changes:
Removed standalone reporting application in favor of fully featured standalone GUI with security login levels and access

New in ApexSQL Audit 2018.04.1438 (Jun 27, 2018)

New in ApexSQL Audit 2018.03.1429 (May 7, 2018)

New in ApexSQL Audit 2018.02.1425 (Mar 27, 2018)

New in ApexSQL Audit 2018.01.1409 (Jan 5, 2018)

Enhancements:
Relative date filter
Multiple client application instances support
High DPI and 4K resolution support
Auditing configuration for GDPR standard is added
Out-of-the-box report for GDPR standard is added
Scheduled reports can now be run on demand
Fixes:
Filters are not applied to scheduled reports
Previews are not created if central repository is larger than 50GB
Multi-select in report preview does not work
Application performs checks vs before-after database even when before-after auditing is not configured
Database auditing configurations cannot be implemented in specific case
All checkboxes are not checked when "Check all" checkbox is used
The "Error changing configuration. Settings will be reverted" error is encountered when switching from simple to advanced filter if include/exclude objects, logins or application options are configured in the simple filter
The add database screen shows only server level operations that can be selected but not related to databases
Remove auditing instance is turned off and needs to be manually started after application update is performed
The database list and object list forms are empty in a specific case
Quarantine folder is not automatically cleared when quarantined items are processed
The application freezes and has to be closed via task manager if the timeout is hit when checking for server-side components on remote instances
Configured auditing filters disappear from the server list in a specific case
Generating a report to excel file fails if cell value exceeds 32767 characters
Application fails to inform the user if the database that is not an actual repository archive is added as a datasource
The "end time" can be set before "start time" which makes created schedule unusable
The "Error running report schedules" error is encountered if reports couldn’t be generated before the generation timeout elapses
The "The system cannot find the file specified" error is encountered if accessing temporary folder that cannot be accessed from the central instance
The "Value cannot be null. Parameter name: source" error is encountered when Send logs button is used in ApexSQL Audit Reports
SQL Server 2017 is not shown in the "add server" form if default instance naming is used
Changes:
New light, blue and dark themes are now available
The application now requires Microsoft .NET Framework 4.7.1

New in ApexSQL Audit 2017.05.1379 (Nov 9, 2017)

New in ApexSQL Audit 2017.04.1362 (Jul 12, 2017)

New in ApexSQL Audit 2017.03.1358 (Jun 14, 2017)

Fixes:
Clustered servers added for auditing are not listed in the Servers list in Configuration tab
Application fails to run if FIPS Windows feature is enabled
The "Index was outside the bounds of the array" error is encountered when verifying central repository database if repository archives have been created in ApexSQL Audit 2017 R2
Update of existing archives to the latest version fails if 'archive old database' option is checked when upgrading to 2017 R2
If the same query with identical SQL update is executed multiple times in a row, audited information on before-after auditing will not include event detail in the report preview
If there is a substantial number of before-after events in the current repository, update to the 2017 version will not complete successfully due to timeout limitations and the process will roll back
The 'value cannot be null' error is encountered when configuring before-after auditing in specific case
The 'Agent unresponsive' error is encountered If timeout value is set to 0 in the installation wizard
The "System.NullReferenceException" error is encountered when clicking on "Advanced" button in Reports tab in a specific case
Email alerts will not be sent if alert title has multiple rows of text
The "Column name 'BeforeAfterCrypt' in table ApexSQL.BeforeAfterChange is specified more than once" error is encountered during application update in specific case
The "There is already an object named 'BeforeAfterChangeView' in the database" error is encountered when upgrading from 2015 to 2017 R2 version
The "An error occurred while processing request on central instance" error is encountered when adding 2015 archives as data sources in the Options dialog
If a database different to the repository archive is added as a datasource, all reports will be empty
Application log file grows in size due to constant error "Error while processing errors from DB: System.Data.SqlClient.SqlException (0x80131904): Could not find stored procedure 'ListLogRecordBatch'." being written in it
The before-after triggers created by ApexSQL Audit are not removed on application uninstall
Export to network share does not complete in case CSV format is selected when exporting
Link to download page does not work in the message displayed on update check
Report templates are not sorted alphabetically within their respective categories
When a report is saved, active report preview is cleared
The "Unhandled exception has occurred in your application..." error is encountered when provided SQL Server name is incorrect during the ApexSQL Audit central instance setup
The “Filter settings changed” warning is displayed when user opens any option from Compliance form and cancels the profile
The 'login failed' unauthorized access event is captured if before-after database is not installed on the central instance
New database created via Archive feature does not retain existing permissions on the initial database
The "Temporary file location" option is missing 'browse for folder' in add server dialog
It is not possible to choose which central instance to connect to in report application if there are multiple central instances present in the network/domain
Text is not wrapped in the Alert summary form
Frames on forms are not consistent in color
Scrolling through report preview with mouse goes slower than through all other forms or when using arrow-keys
Report filters cannot use entries/names with comma
If remotely audited instance is not connectable, server side components installation fix wizard is started if instance is selected in GUI
The merge/overwrite prompt is shown when implementing compliance configuration even if there is no existing filter to overwrite
When compliance template is chosen, all added databases are added automatically

New in ApexSQL Audit 2017.02.1346 (May 4, 2017)

New in ApexSQL Audit 2017.01.1336 (Apr 20, 2017)

Enhancements:
Auditing configuration templates, custom reports, and alert templates can now be exported and imported
Predefined configuration templates and reports for seven compliance standards
Alert recipient lists and alerting profiles
Support for SQL Server 2017 CTP1
Before-after data encryption (AES 256)
Remote auditing instance credentials and temporary folder are now configurable in server configuration pane
Filter conditions are now available for before-after auditing reports
Up to 200% faster auditing of SQL queries containing over 20,000 characters
Navigation through before-after configuration panel is up to 1000% faster when there are more than 100 tables added for auditing
Added progress indicator when adding tables in the before-after auditing panel
Remote installation on domain based setups is now available
Fixes:
Custom value cannot be added in alerts configuration
Operations for internal events cannot be specified
Text data is cut in the report preview if the text is larger than the current application window size
F1 keyboard key doesn’t open help
Missing check all button in object filter
Scrollbar in report preview panel changes in size during the scroll
Alerts cannot be grouped by severity in alert history
The Server filter cannot show servers with a backslash character between the machine name and the SQL Server name in the report preview
The application may crash when making changes to the before-after configuration in specific case
The application installer dialogs are not properly shown on very high resolution (4k)
Alert name in the alert summary is not checked for validity
The trace filter is applied incorrectly when login and application filters are set per database in the advanced filter causing audited data to not be collected
The application is no longer activated and stops working on virtual machines after a virtual machine update, configuration change, or power outage
Advanced filter selected values field is missing in the Object browser dialog
Comma is used as a separator in advanced filter preventing usage of applications and names which contain comma
Microsoft account is not recognized in auditing filters and must be manually typed
The 'is not' condition cannot be used for operations in reports
Before-after auditing doesn't start after the configuration until at least one database is added in the simple filter
Simple filter cannot be applied if unsaved empty condition exists in the advanced filter
The application cannot see local SQL Server instances on x86 operating systems
General overview shows the number of SQL Server cluster nodes as the number of audited instances when a SQL Server failover cluster is audited
The application components size is incorrect in the installer wizard
Copying before-after event doesn't copy the event data in report preview
The New data sources dialog is missing drop-menus for servers and databases
Add table dialog is stuck when loading tables from a database with very large number of objects
Multiple values cannot be entered for client host condition
The ‘An error occurred while processing request on central instance’ error is encountered when creating a custom report with login filter which includes back slash
The “.NET Framework error occurred during execution of user defined routine or aggregate
System.Data.SqlClient.SqlException.NET” error is encountered when making changes to the database that is added for before-after auditing in specific cases
Canceling any warning message during the application installation aborts the installation process
Node name is used in the reports preview instead of the actual failover cluster server name
Row wrapping doesn't work in the summary panel
The 'Cannot import dll VclStylesinno.dll' error is encountered when main application is uninstalled by a user that did not install the tool initially
Application crashes when database with SQL_Latin1_General_CP1_CI_AS collation is added for before-after auditing
Operation ID is shown instead of the operation name when exporting to CSV format
The installation of server-side components failed. Cannot opened archived database” error is encountered during the application upgrade if the archived database has been moved or deleted
The application shows object alias instead of object name in reports
Insert and update statements on temporary tables with joins to real tables are shown as operations on the real tables instead on the temporary in the reports
Before-after auditing doesn't work on case sensitive databases
The 'Windows local time' cannot be selected in the options dialog reporting tab
Changes:
Complete UI redesign with emphasis on usability
Central repository database archiving is no longer mandatory on application update
Web reporting module has been deprecated in favor of “Reporting application” which includes all report related features can now be installed as a separate component and can share report configurations with the central instance

New in ApexSQL Audit 2016.03.1293 (Jun 25, 2016)

New in ApexSQL Audit 2016.02.1291 (Apr 8, 2016)

Enhancements:
The application can now filter excluded applications and logins directly on the SQL Server trace level
Fixes:
The application incorrectly detects the target object when insert and select operations are executed against the temporary table
The auditing instance cannot process trace files timely when a high-performance machine used allows to SQL Server to process and save trace files in real time
The backup and restore filters will not audit events if a database is not added for auditing even when it is classified as the server level filter
The "Failed to collect the trace file: .trc. Trace will be moved to quarantine folder. Error Message: Value cannot be null." error is encountered and application can stop processing the trace files with the valid data
The advanced "Contain" and "Does not contain" filters expressions are causing the trace file cannot be processed
Incorrect info is displayed in the archive database dialog indicates that archived database needs to be added as a datasource when creating reports
The "Are you sure you want to delete..." prompt is missing when deletion of an alert is initiated
Archived databases are not sorted historically in the verify integrity dialog drop down menu
Export report drop down menu doesn't open save as dialog, only selects the format
Saving a custom report clears the current preview
Adding or removing a column from custom report will clear the report preview
When previewing report with less pages than a current preview displays, it will show 'no events found' instead of showing the page in the new preview
Restoring application window back after being minimized, will not restore active warning dialogs
A non-informative message appears when Invalid activation code is inserted
UI issues in the Activation and Uninstall windows
UI issues in the Login(s) window
The "Unable to generate preview: Sequence contains no matching element" is shown instead of preview box for custom alerts
The Bin folder and belonging files will not be removed after uninstalling the auditing instance if it is automatically upgraded to the latest version from the central instance
Changes:
The "Drop database" and "Alter database" events have been moved from the database to server category in simple filter
Internal events are not selected by default in Common reports anymore
The following events have been renamed and moved from server to database category in simple filter
Create DML trigger -> Create trigger
Drop DML trigger -> Drop trigger

New in ApexSQL Audit 2016.01.1285 (Mar 21, 2016)

Enhancements:
Application now supports alerts logging into Windows Event Log
Reports can now use multiple data sources simultaneously
Advanced application status with detail info about central and auditing instances
CLI for exporting reports to any of supported file format
Improved alerts editor with variables highlighting and result preview
SQL Server 2016 CTP3 support for before-after auditing is added
Fixes:
The add firewall exception will open the target port completely, instead only for the application
The Windows taskbar is not shown on hover, when the Auto-hide the taskbar option is checked, and the application is maximized
Pressing the cancel button in the "remove server" dialog removes that SQL Server instance
Incorrect auditing instance status and trace collection is shown when application trial expires
Wrong disk size requirements is displayed in the installation wizard
CSV export doesn't show the operation name
CSV export is not showing the same status values as other reports
The "Object reference not set to an instance of an object." error is encountered when switching between report columns
The "The system cannot find the file specified" error is encountered when opening already deleted/moved report from application
Adding or removing a column from the custom report will clear the report preview
Saving a custom report clears the preview
Large number of system events related to package loading are stockpiled in file system due to incorrect path to ReceivedPackages folder
Removing any added auditing instance in GUI, except the first one, will always remove the first one, while GUI will still display the old one
Message box disappears to the background when Main window loses focus
The application stop working with warning that activation is expired, while the About windows displays that state is activated as well as the central status tab
When previewing report with less pages than current preview shows, preview shows 'no events found' instead of showing the page in new preview
The "Failed to collect the trace file: filename.trc. Trace will be moved to quarantine folder. Error Message: Value cannot be null." error is encountered and application can stop processing the trace files with the valid data
The instance will be marked as installed in the Add server dialog if previously removed from auditing while it was inaccessible
The "Index was out of range. Must be non-negative and less than the size of the collection" error is encountered when copying a field in the generated report via CTRL+C
The "Detect low disk space alert on instance" alert will stop auditing, but will not start auditing again after state is back below the alert threshold
The SQL Server instance name can be displayed double in the reports drop-down list
The Edit report source dialog have the field "Name", which doesn't have any purpose
Once the central instance start loading data into the repository database, after been stopped previously by the alert, it will log as double event that were executed while alert was still active
The package loading into the repository database will not be started again after condition for the free disc space alert ceased to exists
The Archiving process takes over 5 minutes for almost empty repository database and after finished the repository might not be archived
The application can completely stop internal logging randomly
The report's data source will not be removed from the list without warning after explicit remove is performed, causing the numerous errors in the background
The low space alert for the auditing instance will be triggered in the background but will not be displayed in the alert history
The variables cannot be inserted at the beginning of the line
The CREATE events will be logged in repository without the schema and object or with the wrong schema or object or operation in case when the state of the event is marked as failure
The CREATE TABLE event can be double logged in the repository database if the state of the event is "failure"
The data source cannot be removed in the Reports options dialog
The database list in the Add database dialog of the Simple filter is not sorted in alphabetical order
The variables in the subject field of the alert wizard cannot be added by selecting them from predefined set of variables
The variables in the subject field of the alert wizard are not highlighted
The data integrity alert will be send repeatedly each time when alert checks for integrity, even the new database integrity breach wasn't occurred
The alert filter is missing the client host condition
The Row time column in the Verify audit integrity dialog is empty
The successful UPDATE operation can be marked as failed in the report
The report might display double update events
After stopping the instance via the Stop button, audited instance will be stopped but GUI indication will continue to show as running, and the Start button will be remaining disabled which prevents starting the auditing again
There is no tool tips with description of variables in the alert wizard dialog
There is no preview for the alert details settings in the basic settings dialog of the alert wizard
The application allows selecting and adding the single cluster node of the failover cluster even when auditing instances are installed on all nodes and recognized as the part of the same failover cluster
The application does not validate when adding the failover cluster instance whether the auditing instance exists on all nodes of the same failover cluster
Every restart of the audited service will cause a new distributed processor to be started which multiply the logging of the same event in the repository
The DROP LOGIN event is always stored twice in repository database and displayed twice in reports
The “Prev” and “Next” buttons are missing the < and > signs respectively in all dialogs
Installation of Auditing instance offers to create a shortcut for application
Changes:
Before-after auditing is now CLR trigger based
Before-after auditing reports are now part of the unique reporting system
The Auto growth value for the repository database is set to 1GB to prevent frequent auto growth and consuming too many resources
The central repository ‘PRIMARY' datafile size is set to 5GB by default
The size of the generated trace file is set to 10MB by default

New in ApexSQL Audit 2015.04.1254 (Nov 10, 2015)

New in ApexSQL Audit 2015.03.1239 (Aug 20, 2015)

New in ApexSQL Audit 2015.03.1238 (Aug 15, 2015)

Enhancements:
Before-After data values auditing is added
Fixes:
An email is not sent when alert is triggered
The "installation of server-side components failed. Error upgrading current CRD." error is encountered when upgrading from the 2014 R5 version
Available variables that can be used in the Basic settings dialog of the alert wizard are not listed
The variables in the "Basic settings" dialog of the alert wizard are not highlighted
The Central repository database tampering alert wizard will not remember user defined "Start check at" time
The user defined Central repository database tampering alert mail server configuration will be reset after the GUI restart
The expanded advanced filter selections of the "Server" operator cannot be scrolled up and down
The 'ERROR: System.ArgumentNullException: Value cannot be null' is encountered when auditing instance is stopped via CLI while the GUI is running
The "Error generating the report: Object reference not set to an instance of an object" error is encountered when trying to generate the custom report after removing any grid column
The column will be still displayed in the grid after its removal via the Select columns dialog
The "Object reference is not set to an instance of an object. Source: ApexSQL.Audit.Gui" error is encountered if some columns are removed from the custom reports and after switching focus from reports to any other tab and then selecting the reports tab again
The page number displayed in report is incorrect and significantly larger than the real one
The values cannot be entered by user for the contains/doesn't contain operands in the custom report filter
The 'An error occurred while processing request on central instance' error is encountered when generating XLS report for more than 100.000 events
The Object filter in common reports filters by the object and access objects columns, while custom reports object filters only by the objects column
The 'ApexSql.Comply.Processor.Distributed.Console has stopped working' error is encountered if any of the audited SQL Servers is stopped when application is uninstalled
The start and stop instance CLI commands will not change the state of the equivalent commands and targeted instances in GUI, making for user impossible to determine which instances are stopped
Incorrect 'Report is exporting...' message displays when generating report
There is no indication/information that the report has been exported
Going back through the installation wizard resets the user defined settings
The "Getting objects list from the server" process cannot be completed
Not all report row details will be copied in clipboard using Ctrl-C or the context menu "Copy" command
Instead of adding only missing columns, all selected columns will be added to the column list in the custom report
The 'An error occurred during local report processing. The definition of the report '' is invalid. More than one report item in the report has the name ‘OperationHeaderTextBox...’ error is encountered when same column is added to the report grid more than once
The 'Order by' drop-down list contains all columns including the columns excluded from the report grid
The application shows "full text" instead of "FULLTEXT" in the Text data
Adding 'Auditing instance' component for installation in installer will not update/affect installation disk space requirements
The 'Generate' button is not disabled during the report generation process
The 'add database' dialog is missing select/deselect all databases option
Changes:
The "Limit the number of notifications..." checkbox is removed from the system alerts dialogs
The variable sign "$: is changed to "%" in the "Basic settings" alert wizard dialog

New in ApexSQL Audit 2015.02.1234 (May 21, 2015)

Fixes:
The selected operator in the advanced filter do not provide option to pick from the existing data from the added SQL Servers
After upgrading the central instance, the auditing instances will not be upgraded automatically, after adding the SQL Servers hosted by these auditing instances for auditing
The custom internal and web report display the larger number of events than the "Complete audit trial" report for the same time period selected
There is no validation in selecting conditions for alert, meaning that if one server was set for alert condition, databases can be added from another server, making the alert prone to errors
The redesigned original filter is much harder and less convenient for use, if user opt not to use advanced filter
The Advanced filter allows inserting of the same condition value multiple times
It is not possible to exclude a single SQL Server from the advanced auditing
The EXECUTE AS and the REVERT statements cannot be audited by application
The "Cancel" button in the "Report" options does not work
The OR operator in expression between the parent and the first child, in the indented group, is always disregarded in favor of AND operator, which results in the wrong expression results
The application settings history does not display what settings were changed and how
The "System.ArgumentException: Object must be of type String" error is encountered when a captured SQL statement is too large
The first child OR operator, in the "Advanced filter" feature, is ignored and the AND operator is used instead
The "Application filter" option in the "Reports" feature does not work
The "Loading report data" displays in the bar when trying to preview reports
The "Warning: This product is not activated. Auditing is stopped" falsely warning message is displayed in web reports even the user is under the valid trial period
A redundant type column "Schema" in the object browser for the "Schema name" advanced auditing filter condition
The "About" window wrongly indicates the "Professional version" of the application
Inconsistency between the "Complete audit trial" and the "Logon activity history" reports, as there is a difference in the data where identical reports should be displayed
The "All Servers" button does not disable the main menu buttons, if a single server was previously selected
There is no drop-list menu with available date/time formats
The application randomly stops working and closes when setting the advanced auditing filter
The F1 key does not initiate help in any application form
The "Help" button in the Web reports leads to a wrong page
The "Exclude" filters can be accessed only by clicking on the "Include" link
The "ApexSQL Audit has stopped working" error is encountered in the specific cases on an application restart
The "Generate" button is not disabled during the generation process
A database is not automatically selected after it is added, so access to the database operations is unavailable in a simple auditing filter
The "System.Windows.Markup.XamlParseException: Set property 'System.Windows.FrameworkElement.MaxHeight' threw an exception." error is encountered and will prevent GUI to start
The alert's Server operation filter cannot be set and thus alert cannot be triggered on server level operations
The Send logs cannot collect the logs from the remote auditing instances
The application will stop loading and storing in repository packages stored in the file system and will never start to loading them again
Current active data source CRD connection can be changed
After communication blackout between the audited and central instamce or if cental instance stop working, the data stored by auditing instance in the package folder will not be send to central instance after communication is reestablished
When large reports are exported, they cannot be saved or viewed anymore if it is larger than the available amount of the free RAM memory, which also causing the central instance to stop working
Application will not collect anything when SELECT INTO query condition is set
The alerts will not be triggered for the SELECT INTO statement when the SELECT INTO database operation condition is set
The SELECT filter condition wrongly collects the SELECT INTO statements
The appplication goes into timeout when veryfuing audit integrity of a database with a large number of events
The appplication goes into timeout in case of a large number of events when trying to Preview the report
The "Message of type ApexSql.Comply.Shared messages.CommonReportExportStatusMessage timeouted" errior is encountered when exporting large number of events to CSV format
The applicaton offers a deleted archive database as a source
The main application does not access the selected data source
The web reports can access a selected data source (archive), but only in the preview grid
The web reports can not export due to missing file

New in ApexSQL Audit 2015.01.1221 (Mar 7, 2015)

Enhancements:
Advanced filter for auditing, reports and alerts has been added
Custom local reports can now be created
Alerting for instance and SQL Server connectivity has been added
Alerting based on results of custom SQL scripts has been added
Alert checking interval is now adjustable
Data integrity check for archived databases can now be performed
Fixes:
The application service stops working after some time period and must be started manually
The installer doesn't validate the central instance host server address and allows installation to continue even with wrongly entered server name
The user who have access to repository database using db user account, cannot access and use reports after archiving the repository database
The "Reports" feature doesn't access the repository database via the application service causing that other users cannot create reports unles they ensure acces to the repository database manually
When editing an alert that have more coditions active, only the "When operation" condition will be displayed as active
The "Alerts" feature doesn't distinguish the host OS regional settings causing the wrong interpretation of the repository database size due to changed "." and "," functionality, constantly triggering the repository database size alert
Increasing the number of alerts will proportionally slows down displaying of the Alert reports until it cause the application to stop responding completely
The "System.ArgumentException: Cannot delete a subkey tree because the subkey does not exist" error is encountered during the upgrade process causing that even old version installed will not work anymore
The "VerifyCrdIntegrity" CLI command shoud be changed to "VerifyRepositoryIntegrity"
The "ArchiveCrd" CLI command shoud be changed to "ArchiveRepository"
There is no text data field in reports
The "Failed to remove server" message appears when removing the server that is not accessable, even the instance will be removed after the GUI restart
The application cannot detect when a server cannot be reached and it always displays that all servers are running fine
The application cannot be activated when a host computer is using non standard regional settings
The "Failed to remove server" message appears when removing server that is not accessible
The "Reports" feature displays already redundant and double accessed objects
The opened dialog cannot be closed by using the escape key

New in ApexSQL Audit 2014.05.1211 (Jan 9, 2015)

New in ApexSQL Audit 2014.04.1198 (Jan 9, 2015)

New in ApexSQL Audit 2014.03.1192 (Jan 9, 2015)

Enhancements:
The report form now includes the progress indication and notification status for report exporting functionality
Fixes:
The last common report in the web console list is overlapped by the browser's destination address tooltip
The application's Overview tab indicates that all servers are running fine, even the server’s status indicates that some SQL instances are unresponsive
The data operations history report, wrongly contains the text data that indicate the wrong delete vs. insert operation
The 'The file 'C:\ProgramData\ApexSQL\ApexSQLAudit\Auditing\MSSQLSERVER\LOG\ApexSql.Audit.Service.log' already exists.' error is encountered when trying to upgrade the application with the newer version
The desktop icon will be deleted after updating application to newer version
The Database auditing settings' database list is not sorted in an alphabetical order
The "An error occurred during the processing of updates: Object reference not set to an instance of an object" is encountered when trying to perform an online update
Pressing the Add servers button will increase the number of servers and databases even when user do not add any new server
The installer will report that ASP.Net 4.5 isn't installed on Windows Server 2008R2, even it is enabled and running in the Application tools
The ALTER TABLE statement could be logged as a double event
Pressing the button "Generate" in the local reports when there is no events to displayed in reports will not have any effects and appears like the button/report doesn't work
The Reports' time filter utilize the AM/PM format while report grid displays the 24H time format
The Permission changes per user report doesn't allow events filtering per specified user
The report filters don't provide an option for user to pick from the drop down lists instead of typing directly in the text boxes
Object filtering in the Add objects to filter dialog doesn't work
The logon event state isn't shown in the Logon activity history report
Exporting the custom reports always wrongly result in two exported files
The application wrongly interprets security events and displays the wrong data in reports
The application logs the EXEC events as the unknown operation and thus prevents the event filtering

New in ApexSQL Audit 2014.02.1184 (Jan 9, 2015)

Enhancements:
Reports are available in the application GUI now. The previous versions had only Web reports
An improved operation filter that allows more granular operation selection. Instead of 3 server operation types that existed in earlier versions, 37 server operations are given in the filter now
An improved object filter that allows more granular object selection. Specific objects can be included or excluded from auditing
Three predefined alerts that are raised when the central repository database size, free disk space on the central or audited instance reach their predefined values
Data alerts now support more than 100 operation types
Improved Web report filtering. The same operations that are added to the operation and object filters are added to the Web report filter
The time needed to show an event after it was executed on SQL Server in the report is reduced up to 3,000%
New user interface style
Fixes:
Missing alerts for Login/Logout events
Missing option to review Login/Logout events in application reports
The application cannot log the operations on audited database where fully qualified name is used when the connection is set for non-audited database
The Active traces files occupies large amount of disk space when very high server activity is present due to inability of software to process the data timely
Internal application events are logged and saved in the application repository database, making noise in the reports
The alert cannot remember and accept the "is not" condition, and every alert with "is not" condition will be actually saved with "is" condition and will trigger the alert
The condition which determines when the alert will be triggered changes its state after editing
The alerts for BACKUP MASTER KEY and BACKUP SERVICE MASTER KEY do not work
The Apply option doesn't work properly after changes are made in the object or database filter
The application stops responding when trying to manipulate large number of objects in the Object selection filter
The Global Overview button doesn't respond after SQL Server instance is stopped
The Web report cannot display all columns in display resolutions width lower than 1920 pixels
Mouse right click button checks/unchecks Operations types

New in ApexSQL Audit 2014.02.0075 (Dec 2, 2014)

New in ApexSQL Audit 2014.02.0074 (Dec 2, 2014)

New in ApexSQL Audit 2014.01.0069 (Dec 2, 2014)

New in ApexSQL Audit 2013.01.0064 (Jun 29, 2013)

New in ApexSQL Audit 2013.01.0063 (Apr 22, 2013)

New in ApexSQL Audit 2013.01.0062 (Apr 22, 2013)

New in ApexSQL Audit 2013.01.0061 (Apr 11, 2013)

Enhancements:
The application now supports auditing SQL Azure databases
Enabling or disabling triggers is now up to 50% faster
Include (.inc) files can now be edited via the Template editor
Fixes:
Updating the 2008 version of the application to the 2011 version and then reinstalling the 2011 version results in the application attempting to load the architecture file from the in the wrong location and showing the message "Arhitecture file: C:\Program Files (x86)\ApexSQL\ApexSQLAudit2011\ApexSQL2049.audx doesn't exists"
Selecting one of the "Check insert trigger(s)", "Check delete trigger(s)" or "Check update trigger(s)" options in both the "All items" and "Checked items" submenus of the "Main" grid’s context menu doesn’t result in automatically selecting the appropriate check boxes in the "Main" grid
Changes made using the "Template editor" to a custom audit architecture which has been set as the default, are not saved unless the custom architecture is explicitly loaded
The application starts the auditing process even if a non-existing project has been specified via the CLI without properly notifying the user about the missing project
Using the spacebar to select or deselect the checkboxes in the "Custom row key" panel doesn’t result in the intended selection
Schema changes for non-audited tables are reported even if the "Report schema changes for non-audited tables" option is set to false
10.0 is displayed in the "Status" bar for SQL Server 2012 instead of 11.0
An asterisk is displayed in the title bare as the name of a new, unnamed project
The auditing SQL tables are locked while generating a standard report
Unicode characters in audited data are shown as "?" in the generated reports
Changes made to the position and size of the "Edit key for table" dialog are lost upon its closing
An incorrect application version is displayed in the Add/Remove programs applet of the Windows Control Panel
Renaming any SQL table results in the "Check for schema changes" feature reporting that a SQL table, named with the original name of the renamed SQL table, has been dropped, and that a new SQL table, named with the new name of the renamed SQL table, has been created
The "Template editor" lacks a horizontal scroll bar
The icon used for the "Training" button located in the "Resources" tab of the ribbon differs from the icon used for the same button in other ApexSQL applications
Updating the application to the latest version results in failure to create the auditing SQL triggers due to missing columns in the auditing SQL tables
The "System.ComponentModel.Win32Exception" error is encountered when attempting to open a report in PDF format if no third party application is associated with PDF files
The "Modified date" column in the application’s standard report doesn’t display the time of the change
Attempting to generate any of the auditing reports puts the application in an unresponsive state when auditing more than 200 SQL tables with more than 1000 row each
Using the "Remove this column" option in any report doesn’t remove the column from the report
The title of the "Delete data wizard dialog" is spelled incorrectly

New in ApexSQL Audit 2011.01.0059 (Dec 27, 2012)

New in ApexSQL Audit 2011.01.0057 (Dec 27, 2012)

New in ApexSQL Audit 2011.01.0056 (Dec 27, 2012)

Enhancements:
SQL Server Denali/2012 RC0 databases are now supported for auditing
Progress dialogs have been redesigned across the application for improved accuracy and usability
New Office 2007 style interface with ribbon bar, quick access toolbar, and ApexSQL Audit button has been introduced
New Resources ribbon bar has been introduced for quick access to Help page, Support forum, Training page, FAQs, Knowledge base, Troubleshooting, About and Get Updates dialog boxes
New standard Project Management dialog has been introduced
Project Management dialog now shows recently used projects or projects stored in any folder of choice
Projects can be Pinned/Un-Pined to Recent Projects list on Project Management dialog
Project description can be edited directly from Project Management dialog
Show on Startup' option has been added to Project Management dialog
Startup Action options group has been added to Options dialog to control Project Management dialog behavior. Available choices are 'Show Project Management dialog', 'Show last opened project' and 'None'
Application can now be presented in 3 color schemes: Blue, Silver and Black
Options dialog has been redesigned with new Office 2007 button bar
Manage Data form has been redesigned for improved usability
Tooltips have been implemented for all options in Options and Install Architecture forms
Standard and Aggregate Report forms now detect if there are no data to report on
Application now doesn’t require administrative permissions to start on Windows Vista and later
The following connection options have been added to Project form: 'Execution timeout' and 'Encrypt connection'
Grid toolbar has been implemented on Manage Audit Triggers, Standard and Aggregate Report forms
Standard and Aggregate Reports can now be exported to PDF
Standard Report CSV export performance has been improved
Standard and Aggregate Report forms are now more responsive when working with large data sets (more than 10,000 operations)
The following new arguments have been implemented for /architect_install
CLI switch:
All [a] – install entire architecture
Fixes:
Lookup data is captured on any audited column change not just the one the lookup was created for
Trigger creation script is auto deleted on application close if its size exceeds 3 MB
Application stops responding when connecting to a database without a project
Number of audited fields instead of transactions occurred is shown in Aggregate Reporting form grid
Auditing Triggers can be installed before Auditing Architecture
Changes to float columns are audited with precision loss to 2 digits after dot
Delete Data by Log Size’ criteria is considered even if not selected when deleting data criteria-based in Manage Data form
Watches cannot be removed after clicking empty area in Watches list
Tables cannot be checked with Space button in main grid
Main form is not maximized at application startup
Template Editor Description and Legal fields are not updatable
Standard and Aggregate Reporting forms don't show the resize indicator in the right bottom corner
Old value’ and ‘New value’ columns in Standard Reporting form grid expand to fit the entire value that may cause them to grow too large
Varbinary(max) values longer than 8,000 characters are shown truncated in Standard Reporting form grid
Undefined data” error is encountered when selecting a database containing Fulltext Stoplists
False schema changes get detected if Auditing Triggers generation was cancelled
Auditing Triggers cannot be created for new Tables and columns in CLI
Table isn’t auto selected for auditing when its columns are selected
Last used folders aren’t remembered within a session
Checking/unchecking Auditing Trigger in Manage Triggers form grid expands all groups in the grid
Default button on Edit Key for Table form when clicked disables Primary Key edit
Save changes prompt is shown regardless of project state when auditing triggers generation is initiated from main grid context menu
Scrolling a grid and checking a row not shown originally moves selection back to the first row in a number of places including Fields for pane, Manage Triggers form, etc.
Connect to SQL Server form is shown system modal
NULL values in varbinary columns are shown as ‘0x’ instead of ‘NULL’ in Standard Reporting form grid
Recent projects list in File menu is not working
Query Timeout option default value cannot be changed
Refreshing main grid clears all column filters but leaves the grid filtered
Columns of a new Table aren’t auto selected for auditing when ‘Automatically Check All New Fields’ option is ON
Changes:
Undo Transactions feature has been deprecated
Auditing Architecture handling items have been moved to a newly implemented toolbar in Manage Architecture form
Main menu and toolbar have been removed from Standard and Aggregate Report forms
Export to Excel’ export item has been renamed to ‘Output to CSV’ on Standard and Aggregate Report forms
Earlier deprecated /profile switch has been removed from CLI
Short name of /project CLI switch has been changed to /pr
Default extension for project files has been changed from .axad to .axap
addtrigger CLI switch now requires a list of Tables and columns to create Auditing Triggers for
remtrigger CLI switch now requires a list of Tables to remove Auditing Triggers from

ApexSQL Audit Changelog

What's new in ApexSQL Audit 2023.01.2212.0

New in ApexSQL Audit 2021.01.2093 (Jul 22, 2022)

New in ApexSQL Audit 2021.01.2091 (Jun 22, 2022)

New in ApexSQL Audit 2021.01.2089 (Jun 1, 2022)

New in ApexSQL Audit 2021.01.2085 Patch (Feb 10, 2022)

New in ApexSQL Audit 2021.01.2082 (Dec 16, 2021)

New in ApexSQL Audit 2020.04.2061 Patch (Aug 25, 2021)

New in ApexSQL Audit 2020.04.2060 Patch (Aug 6, 2021)

New in ApexSQL Audit 2020.04.2057 Patch (Jun 24, 2021)

New in ApexSQL Audit 2020.04.2056 Patch (Jun 14, 2021)

New in ApexSQL Audit 2020.04.2054 Patch (May 17, 2021)

New in ApexSQL Audit 2020.04.2052 Patch (Apr 15, 2021)

New in ApexSQL Audit 2020.04.2050 Patch (Mar 4, 2021)

New in ApexSQL Audit 2020.04.2045 Patch (Jan 19, 2021)

New in ApexSQL Audit 2020.04.2038 (Nov 6, 2020)

New in ApexSQL Audit 2020.03.2021 (Aug 17, 2020)

New in ApexSQL Audit 2020.02.1708 (Jun 11, 2020)

New in ApexSQL Audit 2020.01.1705 (Apr 29, 2020)

New in ApexSQL Audit 2019.04.1654 (Apr 2, 2020)

New in ApexSQL Audit 2019.03.1640 (Nov 25, 2019)

New in ApexSQL Audit 2019.02.1638 (Nov 19, 2019)

New in ApexSQL Audit 2019.01.1635 (Oct 7, 2019)

New in ApexSQL Audit 2019.01.1635 (Oct 7, 2019)

New in ApexSQL Audit 2018.09.1618 (Jun 21, 2019)

New in ApexSQL Audit 2018.09.1612 (May 9, 2019)

New in ApexSQL Audit 2018.08.1535 (Feb 6, 2019)

New in ApexSQL Audit 2018.07.1511 (Nov 7, 2018)

New in ApexSQL Audit 2018.06.1506 (Sep 27, 2018)

New in ApexSQL Audit 2018.05.1444 (Jul 23, 2018)

New in ApexSQL Audit 2018.04.1438 (Jun 27, 2018)

New in ApexSQL Audit 2018.03.1429 (May 7, 2018)

New in ApexSQL Audit 2018.02.1425 (Mar 27, 2018)

New in ApexSQL Audit 2018.01.1409 (Jan 5, 2018)

New in ApexSQL Audit 2017.05.1379 (Nov 9, 2017)

New in ApexSQL Audit 2017.04.1362 (Jul 12, 2017)

New in ApexSQL Audit 2017.03.1358 (Jun 14, 2017)

New in ApexSQL Audit 2017.02.1346 (May 4, 2017)

New in ApexSQL Audit 2017.01.1336 (Apr 20, 2017)

New in ApexSQL Audit 2016.03.1293 (Jun 25, 2016)

New in ApexSQL Audit 2016.02.1291 (Apr 8, 2016)

New in ApexSQL Audit 2016.01.1285 (Mar 21, 2016)

New in ApexSQL Audit 2015.04.1254 (Nov 10, 2015)

New in ApexSQL Audit 2015.03.1239 (Aug 20, 2015)

New in ApexSQL Audit 2015.03.1238 (Aug 15, 2015)

New in ApexSQL Audit 2015.02.1234 (May 21, 2015)

New in ApexSQL Audit 2015.01.1221 (Mar 7, 2015)

New in ApexSQL Audit 2014.05.1211 (Jan 9, 2015)

New in ApexSQL Audit 2014.04.1198 (Jan 9, 2015)

New in ApexSQL Audit 2014.03.1192 (Jan 9, 2015)

New in ApexSQL Audit 2014.02.1184 (Jan 9, 2015)

New in ApexSQL Audit 2014.02.0075 (Dec 2, 2014)

New in ApexSQL Audit 2014.02.0074 (Dec 2, 2014)

New in ApexSQL Audit 2014.01.0069 (Dec 2, 2014)

New in ApexSQL Audit 2013.01.0064 (Jun 29, 2013)

New in ApexSQL Audit 2013.01.0063 (Apr 22, 2013)

New in ApexSQL Audit 2013.01.0062 (Apr 22, 2013)

New in ApexSQL Audit 2013.01.0061 (Apr 11, 2013)

New in ApexSQL Audit 2011.01.0059 (Dec 27, 2012)

New in ApexSQL Audit 2011.01.0057 (Dec 27, 2012)

New in ApexSQL Audit 2011.01.0056 (Dec 27, 2012)

New in ApexSQL Audit 2005.03 (Sep 26, 2006)