Refresh BASE64_ENCODE and BASE64_DECODE (PR 10264) (#36219)

* Update include statement for BASE64_ENCODE documentation

This is in SQL Server 2025 as well

* Edit pass

---------

Co-authored-by: Steve Jones <steve.jones@red-gate.com>

Author: rwestMSFT

docs/includes/applies-to-version/_fabric-se-dw.md

@@ -5,4 +5,4 @@ ms.date: 12/29/2025
 ms.service: sql
 ms.topic: include
 ---
-[[!INCLUDE [SQL analytics endpoint](../fabric-se.md)] and [!INCLUDE [fabric-dw](../fabric-dw.md)]](../../sql-server/sql-docs-navigation-guide.md#applies-to)
+:::image type="icon" source="../media/yes-icon.svg" border="false"::: [[!INCLUDE [SQL analytics endpoint](../fabric-se.md)] and [!INCLUDE [fabric-dw](../fabric-dw.md)]](../../sql-server/sql-docs-navigation-guide.md#applies-to)

docs/includes/applies-to-version/sqlserver2025-asdb-asmi-fabricse-fabricdw-fabricsqldb.md

@@ -0,0 +1,9 @@
+---
+author: rwestMSFT
+ms.author: randolphwest
+ms.date: 01/13/2026
+ms.service: sql
+ms.topic: include
+---
+
+[!INCLUDE [Applies to](../../includes/applies-md.md)] [!INCLUDE [SQL Server 2025](_ss2025.md)] [!INCLUDE [Azure SQL Database](../../includes/applies-to-version/_asdb.md)] [!INCLUDE [Azure SQL Managed Instance](_asmi.md)] [!INCLUDE [_fabric-se-dw](_fabric-se-dw.md)] [!INCLUDE [fabric-sqldb](_fabric-sqldb.md)]

docs/t-sql/functions/base64-decode-transact-sql.md

@@ -1,10 +1,10 @@
 ---
 title: "BASE64_DECODE (Transact-SQL)"
-description: "BASE64_DECODE converts a base64 encoded varchar into the corresponding varbinary."
+description: "BASE64_DECODE converts a Base64 encoded varchar into the corresponding varbinary."
 author: abledenthusiast
 ms.author: aaronpitman
 ms.reviewer: wiassaf, randolphwest
-ms.date: 02/28/2025
+ms.date: 01/13/2026
 ms.service: sql
 ms.subservice: t-sql
 ms.topic: reference
@@ -14,19 +14,19 @@ f1_keywords:
   - "BASE64_DECODE"
   - "BASE64_DECODE_TSQL"
 helpviewer_keywords:
-  - "base64 decode [SQL Server], base64 decode"
+  - "Base64 decode [SQL Server], Base64 decode"
   - "BASE64_DECODE function"
-  - "base64 decoding [SQL Server]"
+  - "Base64 decoding [SQL Server]"
 dev_langs:
   - "TSQL"
 monikerRange: "=azuresqldb-current || =fabric || =fabric-sqldb"
 ---
 
 # BASE64_DECODE (Transact-SQL)
 
-[!INCLUDE [asdb-Fabric-SE-fabricDW-fabricsqldb](../../includes/applies-to-version/asdb-fabricse-fabricdw-fabricsqldb.md)]
+[!INCLUDE [sqlserver2025-asdb-asmi-fabricse-fabricdw-fabricsqldb](../../includes/applies-to-version/sqlserver2025-asdb-asmi-fabricse-fabricdw-fabricsqldb.md)]
 
-`BASE64_DECODE` converts a base64-encoded **varchar** expression into the corresponding **varbinary** expression.
+`BASE64_DECODE` converts a Base64-encoded **varchar** expression into the corresponding **varbinary** expression.
 
 :::image type="icon" source="../../includes/media/topic-link-icon.svg" border="false"::: [Transact-SQL syntax conventions](../../t-sql/language-elements/transact-sql-syntax-conventions-transact-sql.md)
 
@@ -58,15 +58,15 @@ The encoded string's alphabet must be that of [RFC 4648 Table 1](https://datatra
   Msg 9803, Level 16, State 20, Line 15, Invalid data for type "Base64Decode"
   ```
 
-- If the data has valid characters, but incorrectly formatted, the function returns error `Msg 9803, State 21`.
+- If the data has valid characters but is incorrectly formatted, the function returns error `Msg 9803, State 21`.
 
-- If the input contains more than two padding characters or padding characters followed by extra valid input the function returns error `Msg 9803, State 23`.
+- If the input contains more than two padding characters or padding characters followed by extra valid input, the function returns error `Msg 9803, State 23`.
 
 ## Examples
 
 ### A. Standard BASE64_DECODE
 
-In the following example, the base64 encoded string is decoded back into varbinary.
+In the following example, the Base64 encoded string is decoded back into **varbinary**.
 
 ```sql
 SELECT BASE64_DECODE('qQ==');
@@ -78,9 +78,9 @@ SELECT BASE64_DECODE('qQ==');
 0xA9
 ```
 
-### B. BASE64_DECODE a standard base64 string
+### B. BASE64_DECODE a standard Base64 string
 
-In the following example, the string is base64 decoded. Note the string contains URL-unsafe characters `=` and `/`.
+In the following example, the string is Base64 decoded. Note the string contains URL-unsafe characters `=` and `/`.
 
 ```sql
 SELECT BASE64_DECODE('yv7K/g==');
@@ -92,9 +92,9 @@ SELECT BASE64_DECODE('yv7K/g==');
 0xCAFECAFE
 ```
 
-### C. BASE64_DECODE varchar url_safe base64 string
+### C. BASE64_DECODE varchar url_safe Base64 string
 
-In contrast to example B, this example base64 string was encoded using RFC 4648 Table 2 (`url_safe`), but can be decoded the same way as example B.
+Unlike example B, this example uses RFC 4648 Table 2 (`url_safe`) to encode the Base64 string. However, you can decode it the same way as example B.
 
 ```sql
 SELECT BASE64_DECODE('yv7K_g');
@@ -106,9 +106,9 @@ SELECT BASE64_DECODE('yv7K_g');
 0xCAFECAFE
 ```
 
-### D. BASE64_DECODE varchar contains characters not in the base64 alphabet
+### D. BASE64_DECODE varchar contains characters not in the Base64 alphabet
 
-This example contains characters that aren't valid base64 characters.
+This example contains characters that aren't valid Base64 characters.
 
 ```sql
 SELECT BASE64_DECODE('qQ!!');
@@ -124,4 +124,3 @@ Invalid data for type "Base64Decode".
 ## Related content
 
 - [BASE64_ENCODE (Transact-SQL)](base64-encode-transact-sql.md)
-

docs/t-sql/functions/base64-encode-transact-sql.md

@@ -1,10 +1,10 @@
 ---
 title: "BASE64_ENCODE (Transact-SQL)"
-description: "BASE64_ENCODE converts the value of a varbinary into a base64 encoded varchar."
+description: "BASE64_ENCODE converts the value of a varbinary into a Base64 encoded varchar."
 author: abledenthusiast
 ms.author: aaronpitman
 ms.reviewer: wiassaf, randolphwest
-ms.date: 02/28/2025
+ms.date: 01/13/2026
 ms.service: sql
 ms.subservice: t-sql
 ms.topic: reference
@@ -14,19 +14,19 @@ f1_keywords:
   - "BASE64_ENCODE"
   - "BASE64_ENCODE_TSQL"
 helpviewer_keywords:
-  - "base64 encode [SQL Server], base64 encode"
+  - "Base64 encode [SQL Server], Base64 encode"
   - "BASE64_ENCODE function"
-  - "base64 encoding [SQL Server]"
+  - "Base64 encoding [SQL Server]"
 dev_langs:
   - "TSQL"
 monikerRange: "=azuresqldb-current || =fabric || =fabric-sqldb"
 ---
 
 # BASE64_ENCODE (Transact-SQL)
 
-[!INCLUDE [asdb-Fabric-SE-fabricDW-fabricsqldb](../../includes/applies-to-version/asdb-fabricse-fabricdw-fabricsqldb.md)]
+[!INCLUDE [sqlserver2025-asdb-asmi-fabricse-fabricdw-fabricsqldb](../../includes/applies-to-version/sqlserver2025-asdb-asmi-fabricse-fabricdw-fabricsqldb.md)]
 
-`BASE64_ENCODE` converts the value of a **varbinary** expression into a base64-encoded **varchar** expression.
+`BASE64_ENCODE` converts the value of a **varbinary** expression into a Base64-encoded **varchar** expression.
 
 :::image type="icon" source="../../includes/media/topic-link-icon.svg" border="false"::: [Transact-SQL syntax conventions](../../t-sql/language-elements/transact-sql-syntax-conventions-transact-sql.md)
 
@@ -55,20 +55,20 @@ Optional integer literal or expression, which specifies whether the output of th
 
 ## Remarks
 
-The encoded string alphabet is that of [RFC 4648 Table 1](https://datatracker.ietf.org/doc/html/rfc4648#section-4) and might add padding. The URL-safe output uses the base64url alphabet of [RFC 4648 Table 2](https://datatracker.ietf.org/doc/html/rfc4648#section-5) and doesn't add padding. This function doesn't add any new line characters.
+The encoded string uses the alphabet from [RFC 4648 Table 1](https://datatracker.ietf.org/doc/html/rfc4648#section-4) and might include padding. The URL-safe output uses the Base64URL alphabet from [RFC 4648 Table 2](https://datatracker.ietf.org/doc/html/rfc4648#section-5) and doesn't include padding. This function doesn't add any new line characters.
 
 In each case, the database default collation is used. For more information on the supported collations in [!INCLUDE [fabric](../../includes/fabric.md)], see [Tables](/fabric/data-warehouse/tables#collation).
 
-If `url_safe` is true, the base64url string that is generated is incompatible with SQL Server's XML and JSON base64 decoders.
+If you set `url_safe` to true, the generated Base64URL string isn't compatible with SQL Server's XML and JSON Base64 decoders.
 
 ## Examples
 
 ### A. Standard BASE64_ENCODE
 
-The following example returns the base64 encoded value for the `©` symbol.
+The following example returns the Base64 encoded value for the `©` symbol.
 
 ```sql
-SELECT Base64_Encode(0xA9) AS "Encoded © symbol";
+SELECT BASE64_ENCODE(0xA9) AS "Encoded © symbol";
 ```
 
 [!INCLUDE [ssResult_md](../../includes/ssresult-md.md)]
@@ -79,7 +79,7 @@ qQ==
 
 ### B. BASE64_ENCODE a string
 
-In the following example, a string is base64 encoded. The string must first be casted to a varbinary.
+In the following example, a string is Base64 encoded. You must first cast the string to a **varbinary**.
 
 ```sql
 SELECT BASE64_ENCODE(CAST ('hello world' AS VARBINARY));
@@ -93,7 +93,7 @@ aGVsbG8gd29ybGQ=
 
 ### C. BASE64_ENCODE default vs url_safe
 
-In the following example, the first select doesn't specify `url_safe`; however, the second select does specify `url_safe`.
+In the following example, the first `SELECT` statement doesn't specify `url_safe`; however, the second `SELECT` statement does specify `url_safe`.
 
 ```sql
 SELECT BASE64_ENCODE(0xCAFECAFE);
@@ -120,4 +120,3 @@ yv7K_g
 ## Related content
 
 - [BASE64_DECODE (Transact-SQL)](base64-decode-transact-sql.md)
-