Includes updates to ApexSQL Audit, Backup and Job.
Features
- New in ApexSQL Audit 2018.6
- 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.
- New in ApexSQL Backup 2018.04
- New error handling and send logs functionality.
- Improved application installer with a dark theme.
- New application icon.
- New in ApexSQL Job 2018.02
- New error handling and send logs functionality.
- Improved application installer with a dark theme.
- New application icon.
- Delete operation can be run on multiple jobs.
Fixes
- Fixes in ApexSQL Audit 2018.6
- 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.
- 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.
- Fixes in ApexSQL Backup 2018.04
- Installer and product shortcut icons are not scaling automatically.
- "Object reference not set to an instance of an object." error is encountered when Restore files or filegroups button is clicked in History tab.
- "Object reference not set to an instance of an object." error is encountered when a schedule is saved for log shipping jobs.
- "Index was outside the bounds of the array" error is encountered when schedules are created through the command line interface.
- Fixes in ApexSQL Job 2018.02
- "Object reference not set to an instance of an object" error is encountered when navigating to History tab and there are jobs without execution steps defined on the server.
- "Unable to cast object of type 'ApexSql.JobManager.Presenters.AlertsListPresenter' to type 'ApexSql.JobManager.Presenters.SchedulesListPresenter'" error is encountered when clicking on the SQL Server instance in the server tree view right after connecting to the same instance.
- "Object reference not set to an instance of an object." error is encountered when Windows user account that runs the application has limited access to ProgramData folder.
- "Add at least two servers to the server pane" message is encountered when copying a job, and only one server is registered in the server pane.
- View release notes link in setup wizard leads to Download page.
- Updater options are not available in Options form.
- Legal information for exported job lists contains excess "Ã" character.