You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: azure-sql/database/auditing-overview.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ description: SQL Auditing for Azure SQL Database and Azure Synapse Analytics tra
5
5
author: sravanisaluru
6
6
ms.author: srsaluru
7
7
ms.reviewer: wiassaf, vanto, mathoma
8
-
ms.date: 04/26/2023
8
+
ms.date: 05/31/2023
9
9
ms.service: sql-database
10
10
ms.subservice: security
11
11
ms.topic: conceptual
@@ -37,11 +37,12 @@ You can use SQL Database auditing to:
37
37
-**Analyze** reports. You can find suspicious events, unusual activity, and trends.
38
38
39
39
> [!IMPORTANT]
40
-
> Auditing for Azure SQL Database, Azure Synapse and Azure SQL Managed Instance is optimized for availability and performance of the database or instance being audited. During periods of very high activity or high network load, the auditing feature may allow transactions to proceed without recording all of the events marked for auditing.
40
+
> Auditing for Azure SQL Database, Azure Synapse Analytics SQL pools, and Azure SQL Managed Instance is optimized for availability and performance of the database or instance being audited. During periods of very high activity or high network load, the auditing feature may allow transactions to proceed without recording all of the events marked for auditing.
41
41
42
42
## Auditing limitations
43
43
44
-
- Enabling auditing on a paused **Azure Synapse** isn't supported. To enable auditing, resume Azure Synapse.
44
+
- Enabling auditing on a paused **Azure Synapse SQL pool** isn't supported. To enable auditing, resume the **Synapse SQL pool**.
45
+
- Enabling auditing by using User Assigned Managed Identity (UAMI) isn't supported on **Azure Synapse**.
45
46
- Auditing for **Azure Synapse SQL pools** supports default audit action groups **only**.
46
47
- When you configure the auditing for your [logical server in Azure](logical-servers.md) or Azure SQL Database with log destination as the storage account, the target storage account must be enabled with access to storage account keys. If the storage account is configured to use Azure AD-only authentication and not configured for access key usage, auditing can't be configured.
Copy file name to clipboardExpand all lines: docs/data-quality-services/dqs-knowledge-bases-and-domains.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -120,7 +120,7 @@ ms.topic: conceptual
120
120
121
121
- Analyzing the different single domains that make up a composite domain can be a more effective way of assessing data quality.
122
122
123
-
- When you use a composite domain, you can also create cross-domain rules that enable you to verify that the relationship between the data in multiple domains is appropriate. For example, you can verify that the string "London" in a city domain corresponds to the string "England" in a country/region domain. Note that cross-domain rules are taken into consideration after domain rules.
123
+
- When you use a composite domain, you can also create cross-domain rules that enable you to verify that the relationship between the data in multiple domains is appropriate. For example, you can verify that the string "London" in a city domain corresponds to the string "Great Britain" in a country/region domain. Note that cross-domain rules are taken into consideration after domain rules.
124
124
125
125
- Data in composite domains can be attached to a reference data source, in which case the composite domain will be sent to the reference data provider. This is often done with address data.
Copy file name to clipboardExpand all lines: docs/relational-databases/security/sql-server-security-best-practices.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ Azure complies with several industry regulations and standards that can enable y
34
34
35
35
## Column-level protection
36
36
37
-
Organizations often need to protect data at the column level as data regarding customers, employees, trade secrets, product data, healthcare, financial, and other sensitive data is often stored in SQL Server databases. Sensitive columns often include national identification/social security numbers, mobile phone numbers, first name, family name, financial account identification, and any other data that could be deemed personally identifiable information (PII).
37
+
Organizations often need to protect data at the column level as data regarding customers, employees, trade secrets, product data, healthcare, financial, and other sensitive data is often stored in SQL Server databases. Sensitive columns often include identification/social security numbers, mobile phone numbers, first name, family name, financial account identification, and any other data that could be deemed personally identifiable information (PII).
38
38
39
39
The methods and features mentioned in this section raise the level of protection at the column level with minimal overhead, and without requiring extensive changes to application code.
Copy file name to clipboardExpand all lines: docs/reporting-services/html-device-information-settings.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ The following table lists the device information settings for rendering in HTML
20
20
21
21
|Setting|Value|
22
22
|-------------|-----------|
23
-
|**AccessibleTablix**|Indicates whether to render with additional accessibility metadata for use with screen readers. The additional accessibility metadata causes the rendered report to be compliant with the following technical standards in the "Web-based Intranet and Internet Information and Applications" section (1194.22) of the Electronic and Information Technology Accessibility Standards (Section 508) document:<br /><br /> (g) Row and column headers shall be identified for data tables.<br /><br /> (h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers.|
23
+
|**AccessibleTablix**|Indicates whether to render with additional accessibility metadata for use with screen readers. The additional accessibility metadata causes the rendered report to be compliant with the following technical standards in the "Web-based Intranet and Internet Information and Applications" section (1194.22) of the Electronic and Information Technology Accessibility Standards:<br /><br /> (g) Row and column headers shall be identified for data tables.<br /><br /> (h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers.|
24
24
|**ActionScript(\*)**|Specifies the name of the JavaScript function to use when an action event occurs, such as a drillthrough or bookmark click. If this parameter is specified, an action event will trigger the named JavaScript function instead of a postback to the server.|
25
25
|**BookmarkID**|The bookmark ID to jump to in the report.|
26
26
|**DocMap**|Indicates whether to show or hide the report document map. The default value of this parameter is **true**.|
0 commit comments