Applies to

ApexSQL Audit

Summary

In this article, we are going to demonstrate the reporting functionality of the SQL Server auditing tool through the step-by-step scenario that can be utilized to build your own working routine while dealing with the creation of new reporting templates, generating desired output, and configuring scheduled reports.

Problem description:

When ApexSQL Audit is uninstalled, some local files are leftover on the installation drive.

Applies to

ApexSQL Audit

Summary

This article demonstrates how to install and manage the application through the graphical user interface from any workstation in the network.

Applies to

ApexSQL Audit

Summary

An introductory article to feature that helps to achieve greater performances in ApexSQL Audit that publicly became available in 2018.08.1612 version of the product.

Problem Description

Since the central repository database is the tamper-evident environment, what options are there to perform maintenance of the previously collected data without affecting the data integrity checks.

Problem description

There is no text data for the “Configuration update received on server” internal events.

Cause

Internal events are not mandatory to have full text data since ApexSQL Audit is not collecting full data for these events intended for internal investigations and monitoring internal tool processing.

Problem description

Auditing is configured and audited events can be seen in the repository and in the reports, but auditing events are not pulled to the repository for hours/days.

Applies to:

ApexSQL Audit

Summary:

This article describes different approaches to configure ApexSQL Audit to audit large number SQL Server instances.

Applies to

ApexSQL Audit

Summary

This article will explain how to optimize SQL auditing settings to reduce the noise in collected data, improve performance and reduce storage consumption