Merge pull request #33910 from MicrosoftDocs/main

Albertyang0 · web-flow · commit cbc04f0879bd · 2025-04-23T10:29:27.000-07:00
4/23/2025 AM Publish
diff --git a/azure-sql/database/automatic-tuning-email-notifications-configure.md b/azure-sql/database/automatic-tuning-email-notifications-configure.md
diff --git a/azure-sql/managed-instance/timezones-overview.md b/azure-sql/managed-instance/timezones-overview.md
@@ -192,7 +192,7 @@ Using the same time zone across a primary and secondary instance in a failover g
 | India Standard Time | (UTC+05:30) Chennai, Kolkata, Mumbai, New Delhi |
 | Sri Lanka Standard Time | (UTC+05:30) Sri Jayawardenepura |
 | Nepal Standard Time | (UTC+05:45) Kathmandu |
-| Central Asia Standard Time | (UTC+06:00) Nur-Sultan |
+| Central Asia Standard Time | (UTC+06:00) Astana |
 | Bangladesh Standard Time | (UTC+06:00) Dhaka |
 | Omsk Standard Time | (UTC+06:00) Omsk |
 | Myanmar Standard Time | (UTC+06:30) Yangon (Rangoon) |
diff --git a/azure-sql/virtual-machines/windows/failover-cluster-instance-azure-shared-disks-manually-configure.md b/azure-sql/virtual-machines/windows/failover-cluster-instance-azure-shared-disks-manually-configure.md
@@ -38,7 +38,7 @@ Before you complete the instructions in this article, you should already have:
 
 ## Add Azure shared disk
 
-[Deploy a managed with the shared disk feature enabled](/azure/virtual-machines/disks-shared-enable#deploy-shared-disks). Set `maxShares` to **align with the number of cluster nodes** to make the disk shareable across all FCI nodes.
+[Deploy a managed disk with the shared disk feature enabled](/azure/virtual-machines/disks-shared-enable#deploy-shared-disks). Set `maxShares` to **align with the number of cluster nodes** to make the disk shareable across all FCI nodes.
 Premium SSD, Premium SSDv2 and Ultra Disk are supported disk types to use with a SQL Server failover cluster instance. 
 
 Use zone-redundant storage (ZRS) whenever possible. 
diff --git a/docs/sql-server/azure-arc/troubleshoot-telemetry-endpoint.md b/docs/sql-server/azure-arc/troubleshoot-telemetry-endpoint.md
@@ -195,7 +195,7 @@ The following table shows some of the common DPS upload status values and what y
 | `OK` | 200 | The connection is working as expected. |
 |`Bad request`|400|Possible cause: The resource name (SQL Server instance or database name) doesn't conform to Azure resource naming conventions. For example, if the database name is a [reserved word](/azure/azure-resource-manager/troubleshooting/error-reserved-resource-name).|
 | `Unauthorized` | 401 | Likely cause: the extension is configured to send data through an HTTP proxy that requires authentication. Using an HTTP proxy that requires authentication is not currently supported. Use an unauthenticated HTTP proxy or no proxy.|
-| `Forbidden` | 403 | If the Azure Connected Machine agent is otherwise working as expected and this error doesn't resolve itself after a reboot, create a support case with Microsoft Support through the Azure portal.|
+| `Forbidden` | 403 | Check to make sure the `Microsoft.AzureArcData` resource provider is registered on the subscription. If the Azure Connected Machine agent is otherwise working as expected and this error doesn't resolve itself after a reboot, create a support case with Microsoft Support through the Azure portal.|
 | `NotFound` | 404 | The endpoint that the extension is trying to connect to doesn't exist. <br/><br/> To check which endpoint it is trying to connect to, search the logs for `dataprocessingservice`. This condition can happen if the Azure Connected Machine agent was deployed and connected to an Azure region in which the `Microsoft.AzureArcData` resource provider is not yet available. [Redeploy the Azure Connected Machine agent](/azure/azure-arc/servers/manage-agent?tabs=windows#uninstall-the-agent) in a region that the `Microsoft.AzureArcData` resource provider for aSQL Server enabled by Azure Arc is available. See also [Region availability](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/?products=azure-arc).<br/><br/> It is possible that the DNS resolver cache is not refreshed for your machine. To refresh: <br/> - On Windows run: `ipconfig /flushdns`</br> - On Linux (if `systemd` is being used) run: `sudo resolvectl flush-caches` |
 | `Conflict` | 409 | Likely cause: temporary error happening inside of the DPS. If this does not resolve itself, create a support case with Microsoft Support through the Azure portal.|
 | `InternalServerError` | 500 | This is an error that is happening inside of the DPS. Create a support case with Microsoft Support through the Azure portal. |
diff --git a/docs/t-sql/database-console-commands/dbcc-shrinkdatabase-transact-sql.md b/docs/t-sql/database-console-commands/dbcc-shrinkdatabase-transact-sql.md
@@ -4,7 +4,7 @@ description: DBCC SHRINKDATABASE shrinks the size of the data and log files in t
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: umajay, KevinConanMSFT, dplessMSFT, randolphwest
-ms.date: 01/21/2025
+ms.date: 04/22/2025
 ms.service: sql
 ms.subservice: t-sql
 ms.topic: reference
@@ -89,6 +89,8 @@ The database name or ID to be shrunk. 0 specifies that the current database is u
 
 The percentage of free space that you want left in the database file after the shrink operation completes.
 
+If *target_percent* is specified with `TRUNCATEONLY`, free space at the end of the file might not be released.
+
 #### NOTRUNCATE
 
 Moves assigned pages from the file's end to unassigned pages in the front of the file. This action compacts the data within the file. *target_percent* is optional. [!INCLUDE [ssazuresynapse-md](../../includes/ssazuresynapse-md.md)] doesn't support this option.
@@ -99,9 +101,9 @@ The free space at the end of the file isn't returned to the operating system, an
 
 #### TRUNCATEONLY
 
-Releases all free space at the end of the file to the operating system. Doesn't move any pages inside the file. The data file shrinks only to the last assigned extent. Ignores *target_percent* if specified with `TRUNCATEONLY`. [!INCLUDE [ssazuresynapse-md](../../includes/ssazuresynapse-md.md)] doesn't support this option.
+Releases all free space at the end of the file to the operating system. Doesn't move any pages inside the file. The data file shrinks only to the last assigned extent. [!INCLUDE [ssazuresynapse-md](../../includes/ssazuresynapse-md.md)] doesn't support this option.
 
-`DBCC SHRINKDATABASE` with the `TRUNCATEONLY` option affects the database transaction log file only. To truncate the data file, use `DBCC SHRINKFILE` instead. For more information, see [DBCC SHRINKFILE](dbcc-shrinkfile-transact-sql.md).
+If *target_percent* is specified with `TRUNCATEONLY`, free space at the end of the file might not be released.
 
 #### WITH NO_INFOMSGS
 
diff --git a/docs/t-sql/database-console-commands/dbcc-shrinkfile-transact-sql.md b/docs/t-sql/database-console-commands/dbcc-shrinkfile-transact-sql.md
@@ -4,7 +4,7 @@ description: "DBCC SHRINKFILE shrinks the size of a database file."
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: umajay, dpless, randolphwest
-ms.date: 01/21/2025
+ms.date: 04/22/2025
 ms.service: sql
 ms.subservice: t-sql
 ms.topic: reference
@@ -89,6 +89,8 @@ This option isn't supported for FILESTREAM filegroup containers.
 
 If specified, `DBCC SHRINKFILE` tries to shrink the file to *target_size*. Used pages in the file's area to be freed are moved to free space in the file's kept areas. For example, with a 10-MB data file, a `DBCC SHRINKFILE` operation with an `8` *target_size* moves all used pages in the file's last 2 MB into any unallocated pages in the file's first 8 MB. `DBCC SHRINKFILE` doesn't shrink a file past the needed stored data size. For example, if 7 MB of a 10-MB data file is used, a `DBCC SHRINKFILE` statement with a *target_size* of 6 shrinks the file to only 7 MB, not 6 MB.
 
+If *target_size* is specified with `TRUNCATEONLY`, free space at the end of the file might not be released.
+
 #### EMPTYFILE
 
 Migrates all data from the specified file to other files in the *same filegroup*. In other words, `EMPTYFILE` migrates data from a specified file to other files in the same filegroup. `EMPTYFILE` assures you that no new data gets added to the file, despite this file not being read-only. You can use the [ALTER DATABASE](../../t-sql/statements/alter-database-transact-sql.md) statement to remove a file. If you use the [ALTER DATABASE](../../t-sql/statements/alter-database-transact-sql.md) statement to change file size, the read-only flag is reset, and data can be added.
@@ -109,7 +111,7 @@ This option isn't supported for FILESTREAM filegroup containers.
 
 Releases all free space at the file's end to the operating system but doesn't perform any page movement inside the file. The data file is shrunk only to the last allocated extent.
 
-*target_size* is ignored if specified with `TRUNCATEONLY`.
+If *target_size* is specified with `TRUNCATEONLY`, free space at the end of the file might not be released.
 
 The `TRUNCATEONLY` option doesn't move information in the log, but does remove inactive VLFs from the end of the log file. This option isn't supported for FILESTREAM filegroup containers.
 
diff --git a/docs/t-sql/statements/create-server-audit-transact-sql.md b/docs/t-sql/statements/create-server-audit-transact-sql.md
@@ -129,7 +129,7 @@ Database actions fail if they cause audited events. Actions, which don't cause a
 
 #### AUDIT_GUID = *uniqueidentifier*
 
-To support scenarios such as database mirroring, an audit needs a specific GUID that matches the GUID found in the mirrored database. The GUID can't be modified after the audit is created.
+To support scenarios such as database mirroring or databases participating in an Always On availability group, an audit needs a specific GUID that matches the GUID found in the mirrored database. The GUID can't be modified after the audit is created.
 
 #### OPERATOR_AUDIT
 
