Refresh Format files article and address multiple issues

Author: rwestMSFT

docs/relational-databases/import-export/examples-of-bulk-access-to-data-in-azure-blob-storage.md

@@ -3,7 +3,7 @@ title: "Bulk access to data in Azure Blob Storage"
 description: "Transact-SQL examples that use BULK INSERT and OPENROWSET to access data in an Azure Blob Storage account."
 author: rwestMSFT
 ms.author: randolphwest
-ms.date: 10/04/2022
+ms.date: 12/20/2023
 ms.service: sql
 ms.subservice: data-movement
 ms.topic: conceptual
@@ -12,16 +12,17 @@ helpviewer_keywords:
   - "Azure Blob Storage, bulk import to SQL Server"
   - "BULK INSERT, Azure Blob Storage"
   - "OPENROWSET, Azure Blob Storage"
-monikerRange: ">=sql-server-2017||>=sql-server-linux-2017||=azuresqldb-mi-current"
+monikerRange: ">=sql-server-2017 || >=sql-server-linux-2017 || =azuresqldb-mi-current"
 ---
 # Examples of bulk access to data in Azure Blob Storage
 
-[!INCLUDE[sqlserver2017-asdb](../../includes/applies-to-version/sqlserver2017-asdb.md)]
+[!INCLUDE [sqlserver2017-asdb](../../includes/applies-to-version/sqlserver2017-asdb.md)]
 
 The `BULK INSERT` and `OPENROWSET` statements can directly access a file in Azure Blob Storage. The following examples use data from a CSV (comma separated value) file (named `inv-2017-01-19.csv`), stored in a container (named `Week3`), stored in a storage account (named `newinvoices`).
 
-> [!IMPORTANT]  
-> All the paths to the container and to the files on Blob Storage are **case-sensitive**. If not correct, it might return an error like "Cannot bulk load. The file "file.csv" does not exist or you don't have file access rights."
+All the paths to the container and to the files on Blob Storage are **case-sensitive**. If not correct, it might return an error like the following example:
+
+> Cannot bulk load. The file "file.csv" does not exist or you don't have file access rights.
 
 ## Create the credential
 
@@ -34,12 +35,12 @@ For example:
 ```sql
 CREATE DATABASE SCOPED CREDENTIAL UploadInvoices
 WITH IDENTITY = 'SHARED ACCESS SIGNATURE',
-SECRET = 'sv=2018-03-28&ss=b&srt=sco&sp=rwdlac&se=2019-08-31T02:25:19Z&st=2019-07-30T18:25:19Z&spr=https&sig=KS51p%2BVnfUtLjMZtUTW1siyuyd2nlx294tL0mnmFsOk%3D';
+     SECRET = 'sv=2018-03-28&ss=b&srt=sco&sp=rwdlac&se=2019-08-31T02:25:19Z&st=2019-07-30T18:25:19Z&spr=https&sig=KS51p%2BVnfUtLjMZtUTW1siyuyd2nlx294tL0mnmFsOk%3D';
 ```
 
 ## Known issues
 
-Requests from Azure SQL Database and Azure SQL Managed Instance using SAS tokens may be blocked with the following error:
+Requests from Azure SQL Database and Azure SQL Managed Instance using SAS tokens might be blocked with the following error:
 
 ```text
 Msg 4861, Level 16, State 1, Line 27
@@ -58,11 +59,11 @@ The following example uses an external data source pointing to an Azure storage
 
 ```sql
 CREATE EXTERNAL DATA SOURCE MyAzureInvoices
-    WITH (
-        TYPE = BLOB_STORAGE,
-        LOCATION = 'https://newinvoices.blob.core.windows.net',
-        CREDENTIAL = UploadInvoices
-    );
+WITH (
+    TYPE = BLOB_STORAGE,
+    LOCATION = 'https://newinvoices.blob.core.windows.net',
+    CREDENTIAL = UploadInvoices
+);
 ```
 
 Then the `OPENROWSET` statement adds the container name (`week3`) to the file description. The file is named `inv-2017-01-19.csv`.
@@ -72,18 +73,17 @@ SELECT * FROM OPENROWSET(
    BULK 'week3/inv-2017-01-19.csv',
    DATA_SOURCE = 'MyAzureInvoices',
    FORMAT = 'CSV',
-   FORMATFILE='invoices.fmt',
+   FORMATFILE = 'invoices.fmt',
    FORMATFILE_DATA_SOURCE = 'MyAzureInvoices'
-   ) AS DataFile;
+) AS DataFile;
 ```
 
 Using `BULK INSERT`, use the container and file description:
 
 ```sql
 BULK INSERT Colors2
 FROM 'week3/inv-2017-01-19.csv'
-WITH (DATA_SOURCE = 'MyAzureInvoices',
-      FORMAT = 'CSV');
+WITH (DATA_SOURCE = 'MyAzureInvoices', FORMAT = 'CSV');
 ```
 
 ### Access data in a CSV file referencing a container in an Azure Blob Storage location
@@ -92,11 +92,11 @@ The following example uses an external data source pointing to a container (name
 
 ```sql
 CREATE EXTERNAL DATA SOURCE MyAzureInvoicesContainer
-    WITH (
-        TYPE = BLOB_STORAGE,
-        LOCATION = 'https://newinvoices.blob.core.windows.net/week3',
-        CREDENTIAL = UploadInvoices
-    );
+WITH (
+    TYPE = BLOB_STORAGE,
+    LOCATION = 'https://newinvoices.blob.core.windows.net/week3',
+    CREDENTIAL = UploadInvoices
+);
 ```
 
 Then the `OPENROWSET` statement doesn't include the container name in the file description:
@@ -106,23 +106,22 @@ SELECT * FROM OPENROWSET(
    BULK 'inv-2017-01-19.csv',
    DATA_SOURCE = 'MyAzureInvoicesContainer',
    FORMAT = 'CSV',
-   FORMATFILE='invoices.fmt',
+   FORMATFILE = 'invoices.fmt',
    FORMATFILE_DATA_SOURCE = 'MyAzureInvoices'
-   ) AS DataFile;
+) AS DataFile;
 ```
 
 Using `BULK INSERT`, don't use the container name in the file description:
 
 ```sql
 BULK INSERT Colors2
 FROM 'inv-2017-01-19.csv'
-WITH (DATA_SOURCE = 'MyAzureInvoicesContainer',
-      FORMAT = 'CSV');
+WITH (DATA_SOURCE = 'MyAzureInvoicesContainer', FORMAT = 'CSV');
 ```
 
-## See also
+## Related content
 
-- [CREATE DATABASE SCOPED CREDENTIAL](../../t-sql/statements/create-database-scoped-credential-transact-sql.md)
-- [CREATE EXTERNAL DATA SOURCE](../../t-sql/statements/create-external-data-source-transact-sql.md)
-- [BULK INSERT](../../t-sql/statements/bulk-insert-transact-sql.md)
-- [OPENROWSET](../../t-sql/functions/openrowset-transact-sql.md)
+- [CREATE DATABASE SCOPED CREDENTIAL (Transact-SQL)](../../t-sql/statements/create-database-scoped-credential-transact-sql.md)
+- [CREATE EXTERNAL DATA SOURCE (Transact-SQL)](../../t-sql/statements/create-external-data-source-transact-sql.md)
+- [BULK INSERT (Transact-SQL)](../../t-sql/statements/bulk-insert-transact-sql.md)
+- [OPENROWSET (Transact-SQL)](../../t-sql/functions/openrowset-transact-sql.md)

docs/relational-databases/import-export/format-files-for-importing-or-exporting-data-sql-server.md

@@ -1,74 +1,75 @@
 ---
-title: "Format files to import & export data"
+title: "Format files to import and export data"
 description: When you bulk import to a SQL Server table or bulk export from a table, a format file can store field format information for a data file relative to a table.
 author: rwestMSFT
 ms.author: randolphwest
-ms.date: 08/29/2022
+ms.date: 12/20/2023
 ms.service: sql
 ms.subservice: data-movement
 ms.topic: conceptual
 helpviewer_keywords:
   - "bulk exporting [SQL Server], format files"
   - "bulk importing [SQL Server], format files"
   - "format files [SQL Server]"
-monikerRange: ">=aps-pdw-2016||=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||=azuresqldb-mi-current"
+monikerRange: ">=aps-pdw-2016 || =azuresqldb-current || >=sql-server-2016 || >=sql-server-linux-2017 || =azuresqldb-mi-current"
 ---
 # Format files to import or export data (SQL Server)
 
-[!INCLUDE[SQL Server Azure SQL Database PDW](../../includes/applies-to-version/sql-asdb-asdbmi-pdw.md)]
+[!INCLUDE [SQL Server Azure SQL Database PDW](../../includes/applies-to-version/sql-asdb-asdbmi-pdw.md)]
 
-When you bulk import data into a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] table or bulk export data from a table, you can use a *format file* to store all the format information that is required to bulk export or bulk import data. This includes format information for each field in a data file relative to that table.
+When you bulk import data into a [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] table or bulk export data from a table, you can use a *format file* to store all the format information that is required to bulk export or bulk import data. This includes format information for each field in a data file relative to that table.
 
-[!INCLUDE[ssnoversion](../../includes/ssnoversion-md.md)] supports two types of format files: XML formats and non-XML format files. Both non-XML format files and XML format files contain descriptions of every field in a data file, and XML format files also contain descriptions of the corresponding table columns. Generally, XML and non-XML format files are interchangeable. However, we recommend that you use the XML syntax for new format files because they provide several advantages over non-XML format files. For more information, see [XML Format Files (SQL Server)](../../relational-databases/import-export/xml-format-files-sql-server.md).
+[!INCLUDE [ssnoversion](../../includes/ssnoversion-md.md)] supports two types of format files: XML formats and non-XML format files. Both non-XML format files and XML format files contain descriptions of every field in a data file, and XML format files also contain descriptions of the corresponding table columns. Generally, XML and non-XML format files are interchangeable. However, we recommend that you use the XML syntax for new format files because they provide several advantages over non-XML format files. For more information, see [XML Format Files (SQL Server)](xml-format-files-sql-server.md).
 
 > [!NOTE]  
-> This syntax, including bulk insert, is not supported in Azure Synapse Analytics. [!INCLUDE [Use ADF or PolyBase instead of Synapse Bulk Insert](includes/bulk-insert-synapse.md)]
+> This syntax, including bulk insert, isn't supported in Azure Synapse Analytics. [!INCLUDE [Use ADF or PolyBase instead of Synapse Bulk Insert](includes/bulk-insert-synapse.md)]
 
-## <a id="Benefits"></a> Benefits of format files
+## Benefits of format files
 
-- Provides a flexible system for writing data files that requires little or no editing to comply with other data formats or to read data files from other software.
-- Enables you to bulk import data without having to add or delete unnecessary data or to reorder existing data in the data file. Format files are particularly useful when a mismatch exists between fields in the data file and columns in the table.
+Format files provide a flexible system for writing data files that requires little or no editing to comply with other data formats or to read data files from other software.
 
-## <a id="ExamplesOfFFs"></a> Examples of format files
+You can bulk import data without having to add or delete unnecessary data or to reorder existing data in the data file. Format files can be useful when a mismatch exists between fields in the data file and columns in the table.
 
-The following examples show the layout of a non-XML format file and of an XML format file. These format files correspond to the `HumanResources.myTeam` table in the [!INCLUDE[ssSampleDBobject](../../includes/sssampledbobject-md.md)] sample database. This table contains four columns: `EmployeeID`, `Name`, `Title`, and `ModifiedDate`.
+## Examples of format files
+
+The following examples show the layout of a non-XML format file and of an XML format file. These format files correspond to the `HumanResources.myTeam` table in the [!INCLUDE [ssSampleDBobject](../../includes/sssampledbobject-md.md)] sample database. This table contains four columns: `EmployeeID`, `Name`, `Title`, and `ModifiedDate`.
 
 > [!NOTE]  
-> For information about this table and how to create it, see [HumanResources.myTeam Sample Table &#40;SQL Server&#41;](../../relational-databases/import-export/humanresources-myteam-sample-table-sql-server.md).
+> For information about this table and how to create it, see [HumanResources.myTeam sample table (SQL Server)](humanresources-myteam-sample-table-sql-server.md).
 
 ### A. Use a non-XML format file
 
-The following non-XML format file uses the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] native data format for the `HumanResources.myTeam` table. This format file was created by using the following `bcp` command.
+The following non-XML format file uses the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] native data format for the `HumanResources.myTeam` table. This format file was created by using the following `bcp` command.
 
 ```cmd
 bcp AdventureWorks2022.HumanResources.myTeam format nul -f myTeam.Fmt -n -T
 ```
 
-The `bcp` command defaults to a local, default instance of SQL Server with Windows Authentication. You can specify other instance and login information as desired, for more information see [bcp Utility](../../tools/bcp-utility.md). For example, to specify a remote server named instance with Windows Authentication, use:
+The `bcp` command defaults to a local, default instance of [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)] with Windows Authentication. You can specify other instance and login information as desired, for more information, see [bcp Utility](../../tools/bcp-utility.md). For example, to specify a remote server named instance with Windows Authentication, use:
 
 ```cmd
 bcp AdventureWorks2022.HumanResources.myTeam format nul -f myTeam.Fmt -n -T -S servername/instancename
 ```
 
-The contents of this format file are as follows, starting with the major version number of SQL Server, and the table metadata information.
+The contents of this format file are as follows, starting with the major version number of [!INCLUDE [ssnoversion-md](../../includes/ssnoversion-md.md)], and the table metadata information.
 
 ```output
 14.0
 4
-1       SQLSMALLINT   0       2       ""   1     EmployeeID               ""  
-2       SQLNCHAR      2       100     ""   2     Name                     SQL_Latin1_General_CP1_CI_AS  
-3       SQLNCHAR      2       100     ""   3     Title                    SQL_Latin1_General_CP1_CI_AS  
+1       SQLSMALLINT   0       2       ""   1     EmployeeID               ""
+2       SQLNCHAR      2       100     ""   2     Name                     SQL_Latin1_General_CP1_CI_AS
+3       SQLNCHAR      2       100     ""   3     Title                    SQL_Latin1_General_CP1_CI_AS
 4       SQLNCHAR      2       100     ""   4     Background               SQL_Latin1_General_CP1_CI_AS
 ```
 
-For more information, see [Non-XML Format Files &#40;SQL Server&#41;](../../relational-databases/import-export/non-xml-format-files-sql-server.md).
+For more information, see [Use Non-XML format files (SQL Server)](non-xml-format-files-sql-server.md).
 
-### B. Using an XML format file
+### B. Use an XML format file
 
-The following XML format file uses the [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] native data format for the `HumanResources.myTeam` table. This format file was created by using the following `bcp` command.
+The following XML format file uses the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] native data format for the `HumanResources.myTeam` table. This format file was created by using the following `bcp` command.
 
 ```cmd
-bcp AdventureWorks2022.HumanResources.myTeam format nul -f myTeam.Xml -x -n -T
+bcp AdventureWorks2022.HumanResources.myTeam format nul -f myTeam.xml -x -n -T
 ```
 
 The format file contains:
@@ -91,39 +92,39 @@ The format file contains:
 </BCPFORMAT>
 ```
 
-For more information, see [XML Format Files &#40;SQL Server&#41;](../../relational-databases/import-export/xml-format-files-sql-server.md).
-
-## <a id="WhenFFrequired"></a> When is a format file required?
+For more information, see [XML Format Files (SQL Server)](xml-format-files-sql-server.md).
 
-- An INSERT ... SELECT * FROM OPENROWSET(BULK...) statement always requires a format file.
-- For **bcp** or BULK INSERT, in simple situations, using a format file is optional and rarely necessary. However, for complex bulk-import situations, a format file is frequently required.
+## When is a format file required?
 
-Format files are required if:
+Format files are usually required in the following circumstances:
 
+- When you use an `INSERT ... SELECT * FROM OPENROWSET(BULK...)` statement.
+- For complex bulk-import situations using  **bcp** or `BULK INSERT`.
 - The same data file is used as a source for multiple tables that have different schemas.
 - The data file has a different number of fields that the target table has columns; for example:
 
-  - The target table contains at least one column for which either a default value is defined or NULL is allowed.
-  - The users do not have SELECT/INSERT permissions on one or more columns in the table.
+  - The target table contains at least one column for which either a default value is defined or `NULL` is allowed.
+  - The users don't have `SELECT`/`INSERT` permissions on one or more columns in the table.
   - A single data file is used with two or more tables that have different schemas.
 
 - The column order is different for the data file and table.
 - The terminating characters or prefix lengths differ among the columns of the data file.
 
 > [!NOTE]  
-> In the absence of a format file, if a **bcp** command specifies a data-format switch (**-n**, **-c**, **-w**, or **-N**) or a BULK INSERT operation specifies the DATAFILETYPE option, the specified data format is used as the default method of interpreting the fields of the data file.
+> In the absence of a format file, if a **bcp** command specifies a data-format switch (`-n`, `-c`, `-w`, or `-N`) or a `BULK INSERT` operation specifies the `DATAFILETYPE` option, the specified data format is used as the default method of interpreting the fields of the data file.
 
-## See also
+## Related tasks
 
-- [Non-XML Format Files &#40;SQL Server&#41;](../../relational-databases/import-export/non-xml-format-files-sql-server.md)
-- [XML Format Files &#40;SQL Server&#41;](../../relational-databases/import-export/xml-format-files-sql-server.md)
-- [Data Formats for Bulk Import or Bulk Export &#40;SQL Server&#41;](../../relational-databases/import-export/data-formats-for-bulk-import-or-bulk-export-sql-server.md)
-- [bcp Utility](../../tools/bcp-utility.md)
+- [Using BCP native/format file vs text file and the BOM](https://techcommunity.microsoft.com/t5/sql-server-blog/using-sqlbcp-native-format-file-vs-text-file-and-the-bom/ba-p/3194629)
+- [Use Non-XML format files (SQL Server)](non-xml-format-files-sql-server.md)
+- [XML Format Files (SQL Server)](xml-format-files-sql-server.md)
+- [Data formats for bulk import or bulk export (SQL Server)](data-formats-for-bulk-import-or-bulk-export-sql-server.md)
+- [Create a format file with bcp (SQL Server)](create-a-format-file-sql-server.md)
 
-## <a id="RelatedTasks"></a> Next steps
+## Related content
 
-- [Create a Format File &#40;SQL Server&#41;](../../relational-databases/import-export/create-a-format-file-sql-server.md)
-- [Use a Format File to Bulk Import Data &#40;SQL Server&#41;](../../relational-databases/import-export/use-a-format-file-to-bulk-import-data-sql-server.md)
-- [Use a Format File to Skip a Table Column &#40;SQL Server&#41;](../../relational-databases/import-export/use-a-format-file-to-skip-a-table-column-sql-server.md)
-- [Use a Format File to Skip a Data Field &#40;SQL Server&#41;](../../relational-databases/import-export/use-a-format-file-to-skip-a-data-field-sql-server.md)
-- [Use a Format File to Map Table Columns to Data-File Fields &#40;SQL Server&#41;](../../relational-databases/import-export/use-a-format-file-to-map-table-columns-to-data-file-fields-sql-server.md)
+- [bcp Utility](../../tools/bcp-utility.md)
+- [Use a format file to bulk import data (SQL Server)](use-a-format-file-to-bulk-import-data-sql-server.md)
+- [Use a Format file to skip a table column (SQL Server)](use-a-format-file-to-skip-a-table-column-sql-server.md)
+- [Use a format file to skip a data field (SQL Server)](use-a-format-file-to-skip-a-data-field-sql-server.md)
+- [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)