Merge pull request #33895 from dimitri-furman/dfurman/shrink

Fix truncateonly with target

Author: prmerger-automator[bot]

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
 

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.