Merge pull request #35894 from MicrosoftDocs/WilliamDAssafMSFT-patch-2

Update binary-and-varbinary-transact-sql.md

Author: prmerger-automator[bot]

docs/t-sql/data-types/binary-and-varbinary-transact-sql.md

@@ -1,10 +1,10 @@
 ---
-title: "binary and varbinary (Transact-SQL)"
+title: "Binary and Varbinary (Transact-SQL)"
 description: "Binary data types of either fixed length or variable length."
 author: MikeRayMSFT
 ms.author: mikeray
-ms.reviewer: randolphwest
-ms.date: 09/24/2024
+ms.reviewer: randolphwest, jovanpop
+ms.date: 11/20/2025
 ms.service: sql
 ms.subservice: t-sql
 ms.topic: "reference"
@@ -67,7 +67,7 @@ When other data types are converted to **binary** or **varbinary**, the data is
 
 Converting data to the **binary** and **varbinary** data types is useful if **binary** data is the easiest way to move around data. At some point, you might convert a value type to a binary value of large enough size and then convert it back. This conversion always results in the same value if both conversions are taking place on the same version of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. The binary representation of a value might change from version to version of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].
 
-You can convert **int**, **smallint**, and **tinyint** to **binary** or **varbinary**. If you convert the **binary** value back to an integer value, this value will be different from the original integer value if truncation has occurred. For example, the following SELECT statement shows that the integer value `123456` is stored as a binary `0x0001e240`:
+You can convert **int**, **smallint**, and **tinyint** to **binary** or **varbinary**. If you convert the **binary** value back to an integer value, this value is different from the original integer value if truncation occurred. For example, the following SELECT statement shows that the integer value `123456` is stored as a binary `0x0001e240`:
 
 ```sql
 SELECT CAST( 123456 AS BINARY(4) );
@@ -83,10 +83,10 @@ The following batch shows that this silent truncation can affect arithmetic oper
 
 ```sql
 DECLARE @BinaryVariable2 BINARY(2);
-  
+
 SET @BinaryVariable2 = 123456;
 SET @BinaryVariable2 = @BinaryVariable2 + 1;
-  
+
 SELECT CAST( @BinaryVariable2 AS INT);
 GO
 ```
@@ -96,12 +96,8 @@ The final result is `57921`, not `123457`.
 > [!NOTE]  
 > Conversions between any data type and the **binary** data types are not guaranteed to be the same between versions of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].
 
-## Limitations
-
-Currently, in [!INCLUDE [fabric](../../includes/fabric.md)], only varbinary(*n*) is supported. The binary and varbinary(max) data types are not supported.
-
-## See also
+## Related content
 
-- [CAST and CONVERT (Transact-SQL)](../../t-sql/functions/cast-and-convert-transact-sql.md)
-- [Data Type Conversion (Database Engine)](../../t-sql/data-types/data-type-conversion-database-engine.md)
-- [Data Types (Transact-SQL)](../../t-sql/data-types/data-types-transact-sql.md)
+- [CAST and CONVERT (Transact-SQL)](../functions/cast-and-convert-transact-sql.md)
+- [Data Type Conversion (Database Engine)](data-type-conversion-database-engine.md)
+- [Data Types (Transact-SQL)](data-types-transact-sql.md)