20250617 Azure SQL Database virtualization

WilliamDAssafMSFT · WilliamDAssafMSFT · commit b1c5fb50e591 · 2025-06-17T18:21:27.000-07:00
diff --git a/docs/relational-databases/import-export/use-unicode-character-format-to-import-or-export-data-sql-server.md b/docs/relational-databases/import-export/use-unicode-character-format-to-import-or-export-data-sql-server.md
@@ -3,8 +3,7 @@ title: "Use Unicode Character Format to Import & Export Data"
 description: The Unicode character data format allows data to be exported from a SQL Server instance by using a code page that differs from the code page used by the client.
 author: rwestMSFT
 ms.author: randolphwest
-ms.reviewer: wiassaf
-ms.date: 06/17/2025
+ms.date: 05/27/2025
 ms.service: sql
 ms.subservice: data-movement
 ms.topic: concept-article
@@ -31,11 +30,9 @@ When using Unicode character format, consider:
 
 - The [sql_variant](../../t-sql/data-types/sql-variant-transact-sql.md) data that is stored in a Unicode character-format data file operates in the same way it operates in a character-format data file, except that the data is stored as [nchar](../../t-sql/data-types/nchar-and-nvarchar-transact-sql.md) instead of [char](../../t-sql/data-types/char-and-varchar-transact-sql.md) data. For more information about character format, see [Collation and Unicode support](../collations/collation-and-unicode-support.md).
 
-<a id="special_considerations"></a>
-
 ## Special considerations for Using Unicode character format, bcp, and a format file
 
-Unicode character format data files follow the conventions for Unicode files. The first two bytes of the file are hexadecimal numbers, `0xFFFE`. These bytes serve as byte-order marks (BOM), specifying whether the high-order byte is stored first or last in the file. The [bcp Utility](../../tools/bcp-utility.md) might misinterpret the BOM and cause part of your import process to fail; you might receive an error message similar as follows:
+Unicode character format data files follow the conventions for Unicode files. The first two bytes of the file are hexadecimal numbers, 0xFFFE. These bytes serve as byte-order marks (BOM), specifying whether the high-order byte is stored first or last in the file. The [bcp Utility](../../tools/bcp-utility.md) might misinterpret the BOM and cause part of your import process to fail; you might receive an error message similar as follows:
 
 ```csharp
 Starting copy...
@@ -48,51 +45,6 @@ The BOM might be misinterpreted under the following conditions:
 - The [bcp Utility](../../tools/bcp-utility.md) is used and the `-w` switch is used to indicate Unicode character
 
 - A format file is used
-
-- The first field in the data file is non-character
-
-Consider whether any of the following workarounds are available for your *specific* situation:
-
-- Don't use a format file. An example of this workaround is provided below, see [Using bcp and Unicode Character Format to Import Data without a Format File](#bcp_widechar_import).
-
-- Use the `-c` switch instead of `-w`.
-
-- Re-export the data using a native format.
-
-- Use [BULK INSERT](../../t-sql/statements/bulk-insert-transact-sql.md) or [OPENROWSET BULK](../../t-sql/functions/openrowset-bulk-transact-sql.md). For more information, see [Using BULK INSERT and Unicode Character Format with a Non-XML Format File](#bulk_widechar_fmt) and [Using OPENROWSET and Unicode Character Format with a Non-XML Format File](#openrowset_widechar_fmt).
-
-- Manually insert first record in destination table and then use `-F 2` switch to have import start on second record.
-
-- Manually insert dummy first record in data file and then use `-F 2` switch to have import start on second record. An example of this workaround is provided below, see [Using bcp and Unicode Character Format to Import Data with a Non-XML Format File](#bcp_widechar_import_fmt).
-
-- Use a staging table where the first column is a character data type.
-
-- Re-export the data and change the data field order so that the first data field will be character. Then use a format file to remap the data field to the actual order in the table. For an example, see [Use a format file to map table columns to data-file fields (SQL Server)](use-a-format-file-to-map-table-columns-to-data-file-fields-sql-server.md).
-
-<a id="command_options"></a>
-
-## Command options for unicode character format
-
-You can import Unicode character format data into a table using [bcp](../../tools/bcp-utility.md), [BULK INSERT](../../t-sql/statements/bulk-insert-transact-sql.md), or [OPENROWSET BULK](../../t-sql/functions/openrowset-bulk-transact-sql.md). For a [bcp](../../tools/bcp-utility.md) command or [BULK INSERT](../../t-sql/statements/bulk-insert-transact-sql.md) statement, you can specify the data format in the statement. For an [OPENROWSET BULK](../../t-sql/functions/openrowset-bulk-transact-sql.md) statement, you must specify the data format in a format file.  
-
-Unicode character format is supported by the following command options:  
-
-|Command|Option|Description|  
-|-------------|------------|-----------------|  
-| `bcp` |`-w`|Uses the Unicode character format.|  
-| `BULK INSERT` |`DATAFILETYPE ='widechar'`|Uses Unicode character format when bulk importing data.|  
-| `OPENROWSET` |N/A|Must use a format file.|
-
-> [!NOTE]
->  Alternatively, you can specify formatting on a per-field basis in a format file. For more information, see [Format files to import or export data (SQL Server)](format-files-for-importing-or-exporting-data-sql-server.md).
-
-<a id="etc"></a>
-
-## Example test conditions
-
-<a id="sample_table"></a>
-
-The examples are based on the sample `myWidechar` table and format file. The script creates a test database, a table named `myWidechar` and populates the table with some initial values. Execute the following Transact-SQL in Microsoft [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] (SSMS):
 - The first field in the data file is non-character
 
 Consider whether any of the following workarounds might be available for your *specific* situation:
@@ -141,12 +93,14 @@ CREATE DATABASE TestDatabase;
 GO
 
 USE TestDatabase;
-CREATE TABLE dbo.myWidechar ( 
-    PersonID smallint NOT NULL,
-    FirstName nvarchar(25) NOT NULL,
-    LastName nvarchar(30) NOT NULL,
-    BirthDate date,
-    AnnualSalary money
+
+CREATE TABLE dbo.myWidechar
+(
+    PersonID SMALLINT NOT NULL,
+    FirstName NVARCHAR (25) NOT NULL,
+    LastName NVARCHAR (30) NOT NULL,
+    BirthDate DATE,
+    AnnualSalary MONEY
 );
 
 -- Populate table
@@ -172,52 +126,32 @@ REM Review file
 Notepad D:\BCP\myWidechar.fmt
 ```
 
-> [!IMPORTANT]
-> Ensure your non-XML format file ends with a carriage return\line feed. Otherwise you will likely receive the following error message:
-> 
+> [!IMPORTANT]  
+> Ensure your non-XML format file ends with a carriage return\line feed. Otherwise you might receive the following error message:
+>
 > `SQLState = S1000, NativeError = 0`  
 > `Error = [Microsoft][ODBC Driver 13 for SQL Server]I/O error while reading BCP format file`
 
-<a id="examples"></a>
-
 ## Examples
 
-The examples use [the database and format files created in this article](#example-test-conditions).
-
-<a id="bcp_widechar_export"></a>
+The following examples use the database, and format files created previously.
 
-<a id="using-bcp-and-unicode-character-format-to-export-data"></a>
+### Use bcp and Unicode character format to Export Data
 
-### Use bcp and Unicode Character Format to Export Data
+`-w` switch and `OUT` command. The data file created in this example is used in all subsequent examples. At a command prompt, enter the following commands:
 
-Use the `-w` switch and `OUT` command. 
-
-The data file `myWidechar.bcp` created in this example will be used in subsequent examples. 
-
-Change the location of the code sample from `D:\BCP\myWidechar.bcp` to a file location on your machine. 
-
-At a command prompt, enter the following commands:
-
-```cmd
+```batch
 bcp TestDatabase.dbo.myWidechar OUT D:\BCP\myWidechar.bcp -T -w
 
 REM Review results
 NOTEPAD D:\BCP\myWidechar.bcp
 ```
 
-<a id="bcp_widechar_import"></a>
-
-<a id="using-bcp-and-unicode-character-format-to-import-data-without-a-format-file"></a>
-
-### Use bcp and Unicode Character Format to Import Data without a Format File
+### Use bcp and Unicode character format to Import Data without a format file
 
-The `-w` switch and `IN` command. 
+`-w` switch and `IN` command. At a command prompt, enter the following commands:
 
-Change the location of the code sample from `D:\BCP\myWidechar.bcp` to a file location on your machine. 
-
-At a command prompt, enter the following commands:
-
-```cmd
+```batch
 REM Truncate table (for testing)
 SQLCMD -Q "TRUNCATE TABLE TestDatabase.dbo.myWidechar;"
 
@@ -227,19 +161,13 @@ bcp TestDatabase.dbo.myWidechar IN D:\BCP\myWidechar.bcp -T -w
 REM Review results is SSMS
 ```
 
-<a id="bcp_widechar_import_fmt"></a>
-
-<a id="using-bcp-and-unicode-character-format-to-import-data-with-a-non-xml-format-file"></a>
-
-### Use bcp and unicode character format to import data with a non-XML format file
-
-The `-w` and `-f` switches, and the `IN` command.
+### Use bcp and Unicode character format to Import Data with a non-XML format file
 
-[A workaround will need to be used](#special_considerations) since this example involves bcp, a format file, Unicode character, and the first data field in the data file is non-character. The data file `myWidechar.bcp` will be altered by adding an additional record as a "dummy" record which will then be skipped with the `-F 2` switch.
+`-w` and `-f` switches and `IN` command. A workaround needs to be used since this example involves bcp, a format file, Unicode character, and the first data field in the data file is non-character. See [Special Considerations for Using Unicode character format, bcp, and a format file](#special-considerations-for-using-unicode-character-format-bcp-and-a-format-file) earlier in the article. The data file `myWidechar.bcp` is altered by adding an extra record as a "dummy" record which is then skipped with the `-F 2` switch.
 
 At a command prompt, enter the following commands and follow the modification steps:
 
-```cmd
+```batch
 REM Truncate table (for testing)
 SQLCMD -Q "TRUNCATE TABLE TestDatabase.dbo.myWidechar;"
 
@@ -257,15 +185,9 @@ REM Return data file to original state for usage in other examples
 bcp TestDatabase.dbo.myWidechar OUT D:\BCP\myWidechar.bcp -T -w
 ```
 
-<a id="bulk_widechar"></a>
-
-<a id="using-bulk-insert-and-unicode-character-format-without-a-format-file"></a>
-
-### Use BULK INSERT and unicode character format without a format file
+### Use BULK INSERT and Unicode character format without a format file
 
-The `DATAFILETYPE` argument. 
-
-Execute the following Transact-SQL in Microsoft [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] (SSMS):
+`DATAFILETYPE` argument. Execute the following Transact-SQL in Microsoft [!INCLUDE [ssManStudioFull](../../includes/ssmanstudiofull-md.md)] (SSMS):
 
 ```sql
 TRUNCATE TABLE TestDatabase.dbo.myWidechar; -- for testing
@@ -277,36 +199,23 @@ BULK INSERT TestDatabase.dbo.myWidechar FROM 'D:\BCP\myWidechar.bcp'
 SELECT * FROM TestDatabase.dbo.myWidechar;
 ```
 
-<a id="bulk_widechar_fmt"></a>
-
-<a id="using-bulk-insert-and-unicode-character-format-with-a-non-xml-format-file"></a>
-
-### Use BULK INSERT and unicode character format with a non-XML format file
+### Use BULK INSERT and Unicode character format with a non-XML format file
 
-The `FORMATFILE` argument. 
-
-Execute the following Transact-SQL in Microsoft [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] (SSMS):
+`FORMATFILE` argument. Execute the following Transact-SQL in Microsoft [!INCLUDE [ssManStudioFull](../../includes/ssmanstudiofull-md.md)] (SSMS):
 
 ```sql
 TRUNCATE TABLE TestDatabase.dbo.myWidechar; -- for testing
 
-BULK INSERT TestDatabase.dbo.myWidechar
-   FROM 'D:\BCP\myWidechar.bcp'
-   WITH (FORMATFILE = 'D:\BCP\myWidechar.fmt');
+BULK INSERT TestDatabase.dbo.myWidechar FROM 'D:\BCP\myWidechar.bcp'
+    WITH (FORMATFILE = 'D:\BCP\myWidechar.fmt');
 
 -- review results
 SELECT * FROM TestDatabase.dbo.myWidechar;
 ```
 
-<a id="openrowset_widechar_fmt"></a>
-
-<a id="using-openrowset-and-unicode-character-format-with-a-non-xml-format-file"></a>
+### Use OPENROWSET and Unicode character format with a non-XML format file
 
-### Use OPENROWSET and unicode character format with a non-XML format file
-
-The `FORMATFILE` argument. 
-
-Execute the following Transact-SQL in Microsoft [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] (SSMS):
+`FORMATFILE` argument. Execute the following Transact-SQL in Microsoft [!INCLUDE [ssManStudioFull](../../includes/ssmanstudiofull-md.md)] (SSMS):
 
 ```sql
 TRUNCATE TABLE TestDatabase.dbo.myWidechar; -- for testing
@@ -321,8 +230,6 @@ SELECT * FROM OPENROWSET (
 SELECT * FROM TestDatabase.dbo.myWidechar;
 ```
 
-<a id="RelatedTasks"></a>
-
 ## Related tasks
 
 To use data formats for bulk import or bulk export
diff --git a/docs/t-sql/statements/create-database-scoped-credential-transact-sql.md b/docs/t-sql/statements/create-database-scoped-credential-transact-sql.md
@@ -56,7 +56,7 @@ Specifies the name of the account to be used when connecting outside the server.
 - To import a file from Azure Blob Storage using a managed identity, the identity name must be `MANAGED IDENTITY`.
 - When using Kerberos (Windows Active Directory or MIT KDC) do not use the domain name in the `IDENTITY` argument. It should just be the account name.
 - In a SQL Server instance, if creating a database scoped credential with a Storage Access Key used as the `SECRET`, `IDENTITY` is ignored.
-- `WITH IDENTITY` is not required if the container in Azure Blob storage is enabled for anonymous access. For an example querying Azure Blob storage with `OPENROWSET BULK`, see [Import into a table from a file stored on Azure Blob storage](../functions/openrowset-bulk-transact-sql.md#j-use-openrowset-to-access-several-delta-files-from-azure-data-lake-gen2).
+- `WITH IDENTITY` is not required if the container in Azure Blob storage is enabled for anonymous access. For an example querying Azure Blob storage with `OPENROWSET BULK`, see [Import into a table from a file stored on Azure Blob storage](../functions/openrowset-bulk-transact-sql.md#j-use-openrowset-to-access-several-delta-tables-from-azure-data-lake-gen2).
 - In [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)] and later versions, the REST-API connector replaces HADOOP. For Azure Blob Storage and Azure Data Lake Gen 2, the only supported authentication method is shared access signature. For more information, see [CREATE EXTERNAL DATA SOURCE (Transact-SQL)](create-external-data-source-transact-sql.md).
 - In [!INCLUDE [sssql19-md](../../includes/sssql19-md.md)], the only PolyBase external data source that supports Kerberos authentication is Hadoop. All other external data sources (SQL Server, Oracle, Teradata, MongoDB, generic ODBC) only support Basic Authentication.
 - SQL pools in Azure Synapse Analytics include the following notes:
