Microsoft recently deprecated the use of Azure Table storage for SQL Database Auditing. Use Azure Blob Storage to save your auditing files instead.
If you were using Azure Table Storage for your auditing data, here is a simple step by step on how to move to Azure Blob Storage instead.
On this database, called “Sales”, I am inheriting the auditing settings from the server “auditingdemo”. Auditing is not individually configured for this database, as this is not a supported feature for Auditing with Table Storage (for more details about it, please read the session “Blob/table differences in server auditing policy inheritance”).
To change it from Table to Blob Storage, all you need to do is the following:
- Go to the SQL Database server, and modify it from Table to Blob. (Yes, as simple as that)
- Click Save, and now you have Auditing type Blob at the server level:
That’s it. Now you have blob auditing enabled. If you need to have database level auditing, you may set it at the database level as well, but it is not a recommended setting, as per the feature documentation:
You should avoid enabling both server Blob auditing and database Blob auditing together, unless:
- You need to use a different storage account or retention period for a specific database.
- You want to audit different event types or categories for a specific database than are being audited for the rest of the databases on this server (e.g. if table inserts need to be audited only for a specific database).
You may ask: “What about the auditing data that was in the Table Storage? Will I lose it?
The answer is No. The old data continues in Table Storage, and the new auditing data goes to blob storage from this point onwards.