Netherlands: Software

Introductie van Micorosoft SQL Server 2016

Issue link:

Contents of this Issue


Page 178 of 212

166 C H A P T E R 8 | Improved Azure SQL Database Note When a contained database user connects to the database, the connection string must include the database name to properly authenticate. Auditing SQL Database An important aspect of security management is auditing database activity. All service tiers of SQL Database include an auditing engine that tracks and writes events to an audit log in Azure storage. You can use auditing for regulatory compliance as well as for uncovering data anomalies or potential security issues. You can configure auditing to capture success or failure conditions for the following predefined events: Plain SQL Parameterized SQL Stored procedures Logins Transaction management Auditing configuration In the Azure Management Portal, navigate to the blade for the server hosting your SQL Database, click the All Settings link, click Auditing & Threat Detection, and set the Auditing switch to On. You can then click Storage Details to select an Azure storage account, specify the number of retention days, provide a table name, and set the storage access key as primary or secondary, as shown in Figure 8-4. In that case, all databases inherit the same audit settings. (As an alternative, you can configure audit policies for each SQL Database individually.) When you select Audited Events in the Auditing Settings blade, you can exclude specific success or failure events if you like. Click the Save As Default button at the top of the Auditing Settings blade to complete the setup process. Figure 8-4:.Configuring auditing in the Azure Management Portal.

Articles in this issue

Archives of this issue

view archives of Netherlands: Software - Introductie van Micorosoft SQL Server 2016