Page History
...
The operation is performed as an ONLINE operation (only for supported SQLServer SQL Server versions) keeping the database table(s) available for users. The application checks the SQL Server version and then checks if the index compression type is set to page or none. On the basis of based on the compression type, it performs the Index upgrade query which is set to be an ONLINE operation for any compression type to page compression type. The process then creates the non existing 7 indexes mentioned above, after creation it performs the compression on operation then runs and converts the 7 indexes of the event databases (for each instance added for auditing) to be page compressed. For For environments with large repositoryrepositories, the index rebuilds can take a significant amount of time. If you need to defer the rebuild, the SQL Compliance Manager update process will proceed without rebuilding the indexes and you can choose to rebuild the indexes do so at a later. For new instances, it creates the page compressed type indexes is created by default.
| Info |
|---|
The index upgrade operation is skipped if the compression type is already of set to page compression type. |
...
Running the Index rebuild operation manually
In a few Several SQL Servers versions editions (such as the STANDARD edition), do not support the index creation with the ONLINE property is not supported and therefore rebuild operation to be performed in an ONLINE state. Therefore the operation results in a failure message displayed to the user , instructing them to run the application manually without the ONLINE property.
Before updating the indexes, please ensure that the selected database has sufficient free space to accommodate these changes. For example, if the current size of your database is 1MB in size, the updated database may grow to 2 MB2MB. In this case, the update process would require 1MB of free space.
User can Users are able to run the utility manually with additional parameters in order to build rebuild the indexes without the ONLINE option as follows:
...
The second parameter “ONLINE=OFF” is an optional parameter and is meant to be used only when the index update operation cannot be performed with the ONLINE option.
| Note |
|---|
This operation should only be done during a downtime, since the index creation will acquire a lock on the Events table and the auditing will not work in that duration. |
| Note |
|---|
When the utility is run running manually the Index rebuild operation does not occur as an ONLINE operation. |