Skip to content

Commit 28a8df6

Browse files
authored
Merge pull request #33687 from MicrosoftDocs/main
4/1/2025 PM Publish
2 parents bb9fabb + e180488 commit 28a8df6

11 files changed

+179
-140
lines changed

azure-sql/database/auditing-setup.md

Lines changed: 8 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@ titleSuffix: Azure SQL Database & Azure Synapse Analytics
44
description: This article provides an overview of how to set up Auditing and storing those audits to an Azure storage account, Log Analytics workspace, or Event Hubs destination.
55
author: sravanisaluru
66
ms.author: srsaluru
7-
ms.reviewer: mathoma, vanto
8-
ms.date: 09/17/2024
7+
ms.reviewer: mathoma, vanto, randolphwest
8+
ms.date: 04/01/2025
99
ms.service: azure-sql-database
1010
ms.subservice: security
1111
ms.topic: how-to
@@ -53,8 +53,10 @@ To configure writing audit logs to a storage account, select **Storage** when yo
5353

5454
:::image type="content" source="media/auditing-setup/auditing-select-storage.png" alt-text="Screenshot that shows storage account authentication types for Auditing." lightbox="media/auditing-setup/auditing-select-storage.png":::
5555

56-
> [!NOTE]
57-
> If you are deploying from the Azure portal, make sure that the storage account is in the same region as your database and server. If you are deploying through other methods, the storage account can be in any region.
56+
If you're deploying from the Azure portal, make sure that the storage account is in the same region as your database and server. If you're deploying through other methods, the storage account can be in any region.
57+
58+
> [!WARNING]
59+
> For storage authentication, use Managed Identity. Storage Access Keys pose a security risk because if they are compromised, unauthorized individuals can gain access to your storage account, potentially reading, writing, or deleting your data. To mitigate these risks, it's essential to rotate your keys regularly and use Azure Key Vault to manage and rotate your keys securely.
5860
5961
- The default value for retention period is 0 (unlimited retention). You can change this value by moving the **Retention (Days)** slider in **Advanced properties** when configuring the storage account for auditing.
6062
- If you change retention period from 0 (unlimited retention) to any other value, the retention will only apply to logs written after the retention value was changed. Logs written during the period when retention days were set to unlimited retention are preserved, even after retention is enabled.
@@ -72,15 +74,11 @@ To configure writing audit logs to an event hub, select **Event Hub**. Select th
7274
:::image type="content" source="media/auditing-setup/auditing-select-event-hub.png" alt-text="Screenshot showing the Event hub." lightbox="media/auditing-setup/auditing-select-event-hub.png":::
7375

7476
> [!NOTE]
75-
> If you are using multiple targets like storage account, log analytics, or event hub, make sure you have permissions for all the targets else saving audit configuration would fail as it will try to save the settings for all targets.
76-
77-
## Next steps
78-
79-
> [!div class="nextstepaction"]
80-
> [Use Auditing to analyze audit logs and reports](auditing-analyze-audit-logs.md)
77+
> If you're using multiple targets like storage account, log analytics, or event hub, make sure you have permissions for all the targets else saving audit configuration would fail as it will try to save the settings for all targets.
8178
8279
## Related content
8380

81+
- [Use Auditing to analyze audit logs and reports](auditing-analyze-audit-logs.md)
8482
- [Auditing for Azure SQL Database and Azure Synapse Analytics](auditing-overview.md)
8583
- [What's New in Azure SQL Auditing](/Shows/Data-Exposed/Whats-New-in-Azure-SQL-Auditing)
8684
- [Get started with Azure SQL Managed Instance auditing](../managed-instance/auditing-configure.md)

docs/relational-databases/security/encryption/sql-server-connector-maintenance-troubleshooting.md

Lines changed: 25 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -211,29 +211,30 @@ To learn more about Microsoft Entra ID, read [How Azure subscriptions are relate
211211
`3019` | `ErrorHttpReadData` | `Cannot read response data due to network error.`
212212
`3076` | `ErrorHttpResourceNotFound` | `The server responded 404, because the key name was not found. Make sure the key name exists in your vault.`
213213
`3077` | `ErrorHttpOperationForbidden` | `The server responded 403, because the user doesn't have proper permission to perform the action. Make sure you have the permission for the specified operation. At minimum, the connector requires 'get, list, wrapKey, unwrapKey' permissions to function properly.`
214-
`3100` | `ErrorHttpCreateHttpClientOutOfMemory ` | `Cannot create a HttpClient for AKV operation due to out of memory.`
215-
`3101` | `ErrorHttpOpenSession ` | `Cannot open a Http session due to network error.`
216-
`3102` | `ErrorHttpConnectSession ` | `Cannot connect a Http session due to network error.`
217-
`3103` | `ErrorHttpAttemptConnect ` | `Cannot attempt a connect due to network error.`
218-
`3104` | `ErrorHttpOpenRequest ` | `Cannot open a request due to network error.`
219-
`3105` | `ErrorHttpAddRequestHeader ` | `Cannot add request header.`
220-
`3106` | `ErrorHttpSendRequest ` | `Cannot send a request due to network error.`
221-
`3107` | `ErrorHttpGetResponseCode ` | `Cannot get a response code due to network error.`
222-
`3108` | `ErrorHttpResponseCodeUnauthorized ` | `Server responded 401 for the request. Make sure the client Id and secret are correct, and the credential string is a concatenation of AAD client Id and secret without hyphens.`
223-
`3109` | `ErrorHttpResponseCodeThrottled ` | `Server has throttled the request.`
224-
`3110` | `ErrorHttpResponseCodeClientError ` | `The request is invalid. This usually means the key name is invalid or contains invalid characters.`
225-
`3111` | `ErrorHttpResponseCodeServerError ` | `Server responded a response code between 500 and 600.`
226-
`3112` | `ErrorHttpResourceNotFound ` | `The server responded 404, because the key name was not found. Please make sure the key name exists in your vault.`
227-
`3113` | `ErrorHttpOperationForbidden ` | `The server responded 403, because the user does not have proper permission to perform the action. Please make sure you have the permission for the specified operation. At minimum,'get, wrapKey, unwrapKey' permissions are required.`
228-
`3114` | `ErrorHttpQueryHeader ` | `Cannot query for response header.`
229-
`3115` | `ErrorHttpQueryHeaderOutOfMemoryCopyHeader ` | `Cannot copy the response header due to out of memory.`
230-
`3116` | `ErrorHttpQueryHeaderOutOfMemoryReallocBuffer ` | `Cannot query the response header due to out of memory when reallocating a buffer.`
231-
`3117` | `ErrorHttpQueryHeaderNotFound ` | `Cannot find the query header in the response.`
232-
`3118` | `ErrorHttpQueryHeaderUpdateBufferLength ` | `Cannot update the buffer length when querying the response header.`
233-
`3119` | `ErrorHttpReadData ` | `Cannot read response data due to network error.`
234-
`3120` | `ErrorHttpGetResponseOutOfMemoryCreateTempBuffer ` | `Cannot get response body due to out of memory when creating a temp buffer.`
235-
`3121` | `ErrorHttpGetResponseOutOfMemoryGetResultString ` | `Cannot get response body due to out of memory when get result string.`
236-
`3122` | `ErrorHttpGetResponseOutOfMemoryAppendResponse ` | `Cannot get response body due to out of memory when appending response.`
214+
`3100` | `ErrorHttpCreateHttpClientOutOfMemory` | `Cannot create a HttpClient for AKV operation due to out of memory.`
215+
`3101` | `ErrorHttpOpenSession` | `Cannot open a Http session due to network error.`
216+
`3102` | `ErrorHttpConnectSession` | `Cannot connect a Http session due to network error.`
217+
`3103` | `ErrorHttpAttemptConnect` | `Cannot attempt a connect due to network error.`
218+
`3104` | `ErrorHttpOpenRequest` | `Cannot open a request due to network error.`
219+
`3105` | `ErrorHttpAddRequestHeader` | `Cannot add request header.`
220+
`3106` | `ErrorHttpSendRequest` | `Cannot send a request due to network error.`
221+
`3107` | `ErrorHttpGetResponseCode` | `Cannot get a response code due to network error.`
222+
`3108` | `ErrorHttpResponseCodeUnauthorized` | `Server responded 401 for the request. Make sure the client Id and secret are correct, and the credential string is a concatenation of AAD client Id and secret without hyphens.`
223+
`3109` | `ErrorHttpResponseCodeThrottled` | `Server has throttled the request.`
224+
`3110` | `ErrorHttpResponseCodeClientError` | `The request is invalid. This usually means the key name is invalid or contains invalid characters.`
225+
`3111` | `ErrorHttpResponseCodeServerError` | `Server responded a response code between 500 and 600.`
226+
`3112` | `ErrorHttpResourceNotFound` | `The server responded 404, because the key name was not found. Please make sure the key name exists in your vault.`
227+
`3113` | `ErrorHttpOperationForbidden` | `The server responded 403, because the user does not have proper permission to perform the action. Please make sure you have the permission for the specified operation. At minimum,'get, wrapKey, unwrapKey' permissions are required.`
228+
`3114` | `ErrorHttpQueryHeader` | `Cannot query for response header.`
229+
`3115` | `ErrorHttpQueryHeaderOutOfMemoryCopyHeader` | `Cannot copy the response header due to out of memory.`
230+
`3116` | `ErrorHttpQueryHeaderOutOfMemoryReallocBuffer` | `Cannot query the response header due to out of memory when reallocating a buffer.`
231+
`3117` | `ErrorHttpQueryHeaderNotFound` | `Cannot find the query header in the response.`
232+
`3118` | `ErrorHttpQueryHeaderUpdateBufferLength` | `Cannot update the buffer length when querying the response header.`
233+
`3119` | `ErrorHttpReadData` | `Cannot read response data due to network error.`
234+
`3120` | `ErrorHttpGetResponseOutOfMemoryCreateTempBuffer` | `Cannot get response body due to out of memory when creating a temp buffer.`
235+
`3121` | `ErrorHttpGetResponseOutOfMemoryGetResultString` | `Cannot get response body due to out of memory when get result string.`
236+
`3122` | `ErrorHttpGetResponseOutOfMemoryAppendResponse` | `Cannot get response body due to out of memory when appending response.`
237+
`3128` | `ErrorHttpBadRequest` | `The secret and client id are correct but in the wrong format.`
237238
`3200` | `ErrorGetAADValuesOutOfMemoryConcatPath` | `Cannot get Azure Active Directory challenge header values due to out of memory when concatenating the path.`
238239
`3201` | `ErrorGetAADDomainUrlStartPosition` | `Cannot find the starting position for Azure Active Directory domain Url in malformatted response challenge header.`
239240
`3202` | `ErrorGetAADDomainUrlStopPosition` | `Cannot find the ending position for Azure Active Directory domain Url in malformatted response challenge header.`
@@ -314,7 +315,7 @@ To learn more about Microsoft Entra ID, read [How Azure subscriptions are relate
314315
`3819` | `ErrorPEMCertAuthParamsCreateRequestBody` | `Error creating request body from PEM private key for authentication with AAD.`
315316
`3820` | `ErrorLegacyPrivateKeyAuthParamsSignAlg` | `Error getting RSA signing algorithm for Legacy private key authentication with AAD.`
316317
`3821` | `ErrorLegacyPrivateKeyAuthParamsImportForSign` | `Error importing Legacy private key for RSA signing for authentication with AAD.`
317-
`3822` | `ErrorLegacyPrivateKeyAuthParamsCreateRequestBody ` | `Error creating request body from Legacy private key for authentication with AAD.`
318+
`3822` | `ErrorLegacyPrivateKeyAuthParamsCreateRequestBody` | `Error creating request body from Legacy private key for authentication with AAD.`
318319
`3900` | `ErrorAKVDoesNotExist` | `Error internet name not resolved. This typically indicates the Azure Key Vault is deleted.`
319320
`4000` | `ErrorCreateKeyVaultRetryManagerOutOfMemory` | `Cannot create a RetryManager for AKV operation due to out of memory.`
320321

docs/reporting-services/tools/server-properties-advanced-page-reporting-services.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -81,10 +81,15 @@ Sets header values for all URLs matching the specified regex pattern. Users can
8181
```
8282

8383
> [!NOTE]
84-
> Too many headers may impact performance.
84+
> Too many headers may impact performance.
85+
>
86+
> The ```X-Frame-Options```default response header will block the ability to embed SSRS reports within an iframe html element. Removing this header from the ```<CustomHeaders />``` advanced server property will allow reports to be used within iframes.
87+
> ** It is not recommended to make this change on any report servers that will be hosted on the public internet.**
8588
8689
We recommend validating the configuration of your topology to ensure the set of headers is compatible with your deployment of Reporting Services. It's possible to choose settings that cause errors in browsers if the browsers don't also have the appropriate settings. For example, you shouldn't add an HSTS configuration if your server isn't configured for https. Incompatible headers might result in browser rendering errors.
8790

91+
92+
8893
#### CustomHeaders XML format
8994

9095
```xml

docs/sql-server/azure-arc/backup-local.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -45,6 +45,9 @@ You can also run backups on a **default** schedule:
4545
- Differential backups: every 24 hours
4646
- Transaction log backups: every 5 minutes
4747

48+
> [!WARNING]
49+
> Dropping a database immediately deletes the automated backups for that database, irrespective of the retention period.
50+
4851
## Backup schedule level
4952

5053
You can schedule backups at

docs/ssma/access/what-s-new-in-ssma-for-access-accesstosql.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,10 @@
11
---
2-
title: "What's new in SSMA for Access (AccessToSQL)"
2+
title: "What's New in SSMA for Access (AccessToSQL)"
33
description: Find out about changes to SQL Server Migration Assistant (SSMA) for Access (AccessToSQL) for each release.
44
author: cpichuka
55
ms.author: cpichuka
6-
ms.date: 10/16/2024
6+
ms.reviewer: randolphwest
7+
ms.date: 04/01/2025
78
ms.service: sql
89
ms.subservice: ssma
910
ms.topic: whats-new
@@ -18,6 +19,10 @@ This article lists SQL Server Migration Assistant (SSMA) for Access changes in e
1819

1920
[!INCLUDE [entra-id](../../includes/entra-id-hard-coded.md)]
2021

22+
## SSMA v10.1
23+
24+
The v10.1 release of SSMA for Access contains minor performance improvements and bug fixes.
25+
2126
## SSMA v10.0
2227

2328
The v10.0 release of SSMA for Access contains minor performance improvements, bug fixes, and an enhanced help experience.

docs/ssma/db2/what-s-new-in-ssma-for-db2-db2tosql.md

Lines changed: 13 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
2-
title: "What's new in SSMA for Db2 (Db2ToSQL)"
2+
title: "What's New in SSMA for Db2 (Db2ToSQL)"
33
description: Find out about changes to SQL Server Migration Assistant (SSMA) for Db2 (Db2ToSQL) for each release.
44
author: cpichuka
55
ms.author: cpichuka
66
ms.reviewer: randolphwest
7-
ms.date: 10/16/2024
7+
ms.date: 04/01/2025
88
ms.service: sql
99
ms.subservice: ssma
1010
ms.topic: whats-new
@@ -19,13 +19,22 @@ This article lists SQL Server Migration Assistant (SSMA) for Db2 changes in each
1919

2020
[!INCLUDE [entra-id](../../includes/entra-id-hard-coded.md)]
2121

22+
## SSMA v10.1
23+
24+
The v10.1 release of SSMA for Db2 contains the following changes:
25+
26+
- Conversion enhancements for identity column from Db2 z/OS to SQL Server 2019
27+
- Improve conversion of Db2 stored procedure WITH RETURN clause to Azure SQL Database
28+
- Improve database objects load for Db2
29+
- Appropriate error handling for conversion of identifier REPLACE(STRING, CHAR,CHAR) in Db2
30+
2231
## SSMA v10.0
2332

24-
The v10.0 release of SSMA for DB2 contains the following changes:
33+
The v10.0 release of SSMA for Db2 contains the following changes:
2534

2635
- Improve conversion of FETCH FIRST ROW ONLY syntax
2736
- Improve conversion support of LOCATE_IN_STRING behavior
28-
- Support of range-partitioned tables in DB2-ZOS
37+
- Support of range-partitioned tables in Db2 for z/OS
2938
- Improve handling of INCLUDE clause in indexes
3039

3140
## SSMA v9.5

docs/ssma/mysql/what-s-new-in-ssma-for-mysql-mysqltosql.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
2-
title: "What's new in SSMA for MySQL (MySQLToSQL)"
2+
title: "What's New in SSMA for MySQL (MySQLToSQL)"
33
description: Find out about changes to SQL Server Migration Assistant (SSMA) for MySQL (MySQLToSQL) for each release.
44
author: cpichuka
55
ms.author: cpichuka
66
ms.reviewer: randolphwest
7-
ms.date: 10/16/2024
7+
ms.date: 04/01/2025
88
ms.service: sql
99
ms.subservice: ssma
1010
ms.topic: whats-new
@@ -19,6 +19,10 @@ This article lists SQL Server Migration Assistant (SSMA) for MySQL changes in ea
1919

2020
[!INCLUDE [entra-id](../../includes/entra-id-hard-coded.md)]
2121

22+
## SSMA v10.1
23+
24+
The v10.1 release of SSMA for MySQL contains minor performance improvements and bug fixes.
25+
2226
## SSMA v10.0
2327

2428
The v10.0 release of SSMA for MySQL contains minor performance improvements, bug fixes, and online help viewer support.

0 commit comments

Comments
 (0)