this feature is not available in dw player

In other regions, Blob Auditing is not automatically enabled and has to be turned on programmatically by calling ARM REST API. In locations that support Table Auditing, turning on Blob Auditing automatically enables it in all databases, including SQL Data Warehouses-and that’s expected. On top of that, Blob Auditing behaves differently when enabled on a logical server level in different regions.

In North Europe, the portal allows Table Auditing (table-storage based) to be enabled on the SQL Data Warehouse scope, but it isn’t possible to enable Blob Auditing: For instance, in UK South, the portal offers no options to manage auditing: How to enable audit?Īuditing is disabled by default and the UI experience depends on the region to which the logical server is deployed. This might explain the inconsistent experience people have with Azure Portal compared to the more mature Azure SQL Database. On the surface, it’s a kind of SQL Server, but behind the scenes it’s a different beast altogether. It is based on Parallel Data Warehouse with Generation 2 (optimised computing) generally available, but some regions and performance levels still need to submit support requests. Azure SQL Data Warehouse is relatively new MPP (Massively Parallel Processing architecture) database offering.

Business tends to understand its purpose and requirements and is aware of the attached price tag. To put it simply for anyone new to GRC (which stands for Governance, Risk Management, Compliance), auditing is just like logging, but in a more expensive suit and tie. The first article in a series on “Security Intelligence in Azure PaaS” inspired me to write something on auditing in Azure SQL Data Warehouse.

This feature is not available in dw player