Zurück
-
Titel
Problem with the red exclamation mark on a deleted/renamed table -
Beschreibung
The red exclamation mark appears in ApexSQL Audit UI on a deleted/renamed table -
Lösung
Deleted table:
The expected behavior in the ApexSQL Audit after deleting a table which is still present in Before-After auditing is that the red exclamation mark will not appear until the schema is refreshed in the Before-After configuration filters. Which would mean that after the table has been deleted from the server, you can go to the UI and remove it by unchecking (unselecting) it from the table list on the right and then clicking on the Apply button.
If, by any chance the schema is refreshed before the table is removed from the filters in the UI, the mentioned red exclamation mark will be present, and making any change to the Before-After filters will remove it (simple selecting and unselecting any other table, that is not needed for auditing, from the list and clicking on the Apply).
Renamed table:
The expected behavior in the ApexSQL Audit after renaming a table which is still present under the old name in Before-After auditing configuration is that the red exclamation mark, as well as the new table name on the right-hand list, will not appear until the schema is refreshed in the Before-after configuration filters.
In this case, do exactly the same thing as with deleted tables. Go to the ApexSQL Audit UI (but don't refresh the schema) and remove it by unchecking (unselecting) it from the table list on the right and then clicking on the Apply button. Then select the new name from the table list, set the column configuration and click on the Apply. The new name should be visible after unselecting the old one and again, click on the Apply button.
Therefore, regardless of whether the table already present in Before-After configuration is deleted or renamed, the steps explained above need to be performed to prevent problems with referencing non-existent parameters for queries.
And lastly, let's address the issue of producing a report only for dropped tables that are being audited in Before-After. Even though there is no direct way of referencing Before-After auditing in the filters, an advanced filter can be utilized if the tables in question have characteristic text, something that can be used to distinguish them from others.
For more information on using the ApexSQL Audit advanced filters please check the Advanced SQL auditing filters