Run the Collected Statistics Utility on the ATNA Audit Database Tables
Description
In order to minimize the time that it takes to run management reports based on audit data, or to query the audit tables using a custom query, your audit tables should be optimized with the collected statistics utility.
Instructions
The collected statistics utility requires a representative set of data in your audit tables in order to effectively gather statistics that optimize query performance. After one month of receiving data and having users log in and look up data in your system, run the collected statistics utility on the following ATNA schemas:
-
HS_IHE_ATNA_Repository
-
HS_IHE_ATNA_Repository_Data
If you receive DICOM data, also run the collected statistics utility on the following schema:
-
HS_IHE_ATNA_Repository_DICOMData
If you make a change to your system’s data ingestion, for example adding IHE documents or DICOM data, you should run the collected statistics again after one month of collecting the new data.
As the collected statistics utility uses system resources, it should be run in off hours. Running the utility on a very large audit database with terabytes of data in a live system is not recommended. If a test system has a representative set of data, then one option is to run the utility on the test system and export the result to the live system.
For details on running the collected statistics utility, see Table Statistics for Query Optimizer.