20250617 Azure SQL Database virtualization

WilliamDAssafMSFT · WilliamDAssafMSFT · commit 94d80bce9cca · 2025-06-17T18:48:49.000-07:00
diff --git a/azure-sql/database/data-virtualization-overview.md b/azure-sql/database/data-virtualization-overview.md
@@ -71,7 +71,7 @@ SELECT TOP 10 *
 FROM OPENROWSET(
  BULK 'abs://public@pandemicdatalake.blob.core.windows.net/curated/covid-19/bing_covid-19_data/latest/bing_covid-19_data.parquet',
  FORMAT = 'parquet'
-) AS filerows
+) AS filerows;
 ```
 
 You can continue data set exploration by appending `WHERE`, `GROUP BY` and other clauses based on the result set of the first query.
@@ -101,8 +101,8 @@ A shared access signature (SAS) provides delegated access to files in a storage
 
     ```sql
     -- Create MASTER KEY if it doesn't exist in the database:
-    CREATE MASTER KEY ENCRYPTION BY PASSWORD = '<Some Very Strong Password Here>'
-    GO
+    CREATE MASTER KEY 
+    ENCRYPTION BY PASSWORD = '<Some Very Strong Password Here>';
     ```
     
 1. When a SAS token is generated, it includes a question mark (`?`) at the beginning of the token. To use the token, you must remove the question mark (`?`) when creating a credential. For example:
@@ -111,7 +111,6 @@ A shared access signature (SAS) provides delegated access to files in a storage
     CREATE DATABASE SCOPED CREDENTIAL MyCredential
     WITH IDENTITY = 'SHARED ACCESS SIGNATURE',
     SECRET = 'sv=secret string here';
-    GO
     ```
     
 ### [Managed identity](#tab/managed-identity)
@@ -166,7 +165,7 @@ An external data source is an abstraction that enables easy referencing of a fil
 CREATE EXTERNAL DATA SOURCE MyExternalDataSource
 WITH (
     LOCATION = 'abs://public@pandemicdatalake.blob.core.windows.net/curated/covid-19/bing_covid-19_data/latest'
-)
+);
 ```
 
 When accessing nonpublic storage accounts, along with the location, you also need to reference a database scoped credential with encapsulated authentication parameters. The following script creates an external data source pointing to the file path, and referencing a database-scoped credential.
@@ -176,8 +175,8 @@ When accessing nonpublic storage accounts, along with the location, you also nee
 CREATE EXTERNAL DATA SOURCE MyPrivateExternalDataSource
 WITH (
     LOCATION = 'abs://<privatecontainer>@privatestorageaccount.blob.core.windows.net/dataset/' 
-       CREDENTIAL = [MyCredential];
-)
+       CREDENTIAL = [MyCredential]
+);
 ```
 
 ## Query data sources using OPENROWSET
@@ -336,7 +335,7 @@ FROM OPENROWSET(
  BULK 'yellow/puYear=*/puMonth=*/*.parquet',
  DATA_SOURCE = 'NYCTaxiExternalDataSource',
  FORMAT = 'parquet'
-) AS filerows
+) AS filerows;
 ```
 
 It's also convenient to add columns with the file location data to a view using the `filepath()` function for easier and more performant filtering. Using views can reduce the number of files and the amount of data the query on top of the view needs to read and process when filtered by any of those columns:
@@ -350,7 +349,7 @@ FROM OPENROWSET(
  BULK 'yellow/puYear=*/puMonth=*/*.parquet',
  DATA_SOURCE = 'NYCTaxiExternalDataSource',
  FORMAT = 'parquet'
-) AS filerows
+) AS filerows;
 ```
 
 Views also enable reporting and analytic tools like Power BI to consume results of `OPENROWSET`.
@@ -364,8 +363,7 @@ External tables encapsulate access to files making the querying experience almos
 CREATE EXTERNAL FILE FORMAT DemoFileFormat
 WITH (
  FORMAT_TYPE=PARQUET
-)
-GO
+);
 
 --Create external table:
 CREATE EXTERNAL TABLE tbl_TaxiRides(
@@ -396,7 +394,6 @@ WITH (
  DATA_SOURCE = NYCTaxiExternalDataSource,
  FILE_FORMAT = DemoFileFormat
 );
-GO
 ```
 
 Once the external table is created, you can query it just like any other table:
@@ -445,49 +442,7 @@ ORDER BY
 
 If your stored data isn't partitioned, consider partitioning it to improve query performance.
 
-If you are using external tables, `filepath()` and `filename()` functions are supported but not in the WHERE clause. You can still filter by `filename` or `filepath` if you use them in computed columns. The following example demonstrates this:
-
-```sql
-CREATE EXTERNAL TABLE tbl_TaxiRides (
- vendorID VARCHAR(100) COLLATE Latin1_General_BIN2,
- tpepPickupDateTime DATETIME2,
- tpepDropoffDateTime DATETIME2,
- passengerCount INT,
- tripDistance FLOAT,
- puLocationId VARCHAR(8000),
- doLocationId VARCHAR(8000),
- startLon FLOAT,
- startLat FLOAT,
- endLon FLOAT,
- endLat FLOAT,
- rateCodeId SMALLINT,
- storeAndFwdFlag VARCHAR(8000),
- paymentType VARCHAR(8000),
- fareAmount FLOAT,
- extra FLOAT,
- mtaTax FLOAT,
- improvementSurcharge VARCHAR(8000),
- tipAmount FLOAT,
- tollsAmount FLOAT,
- totalAmount FLOAT,
- [Year]  AS CAST(filepath(1) AS INT), --use filepath() for partitioning
- [Month]  AS CAST(filepath(2) AS INT) --use filepath() for partitioning
-)
-WITH (
- LOCATION = 'yellow/puYear=*/puMonth=*/*.parquet',
- DATA_SOURCE = NYCTaxiExternalDataSource,
- FILE_FORMAT = DemoFileFormat
-);
-GO
-
-SELECT *
-      FROM tbl_TaxiRides
-WHERE
-      [year]=2017            
-      AND [month] in (10,11,12);
-```
-
-If your stored data isn't partitioned, consider partitioning it to improve query performance.
+If you are using external tables, `filepath()` and `filename()` functions are supported but not in the `WHERE` clause. 
 
 <!--
 ### Statistics
diff --git a/docs/t-sql/functions/openrowset-bulk-transact-sql.md b/docs/t-sql/functions/openrowset-bulk-transact-sql.md
@@ -44,7 +44,7 @@ OPENROWSET( BULK 'data_file' ,
 )
 
 <bulk_options> ::=
-   [ , DATASOURCE = 'data_source_name' ]
+   [ , DATA_SOURCE = 'data_source_name' ]
 
    -- bulk_options related to input file format
    [ , CODEPAGE = { 'ACP' | 'OEM' | 'RAW' | 'code_page' } ]
@@ -66,51 +66,6 @@ OPENROWSET( BULK 'data_file' ,
 
 ## Arguments
 
-#### '*provider_name*'
-
-A character string that represents the friendly name (or `PROGID`) of the data provider as specified in the registry. *provider_name* has no default value. Provider name examples are `Microsoft.Jet.OLEDB.4.0`, `SQLNCLI`, or `MSDASQL`.
-
-#### '*datasource*'
-
-A string constant that corresponds to a particular OLE DB data source. *datasource* is the `DBPROP_INIT_DATASOURCE` property to be passed to the `IDBProperties` interface of the provider to initialize the provider. Typically, this string includes the name of the database file, the name of a database server, or a name that the provider understands for locating the database or databases.
-
-Data source can be file path `C:\SAMPLES\Northwind.mdb'` for `Microsoft.Jet.OLEDB.4.0` provider, or connection string `Server=Seattle1;Trusted_Connection=yes;` for `SQLNCLI` provider.
-
-#### '*user_id*'
-
-A string constant that is the user name passed to the specified data provider. *user_id* specifies the security context for the connection and is passed in as the `DBPROP_AUTH_USERID` property to initialize the provider. *user_id* can't be a Microsoft Windows login name.
-
-#### '*password*'
-
-A string constant that is the user password to be passed to the data provider. *password* is passed in as the `DBPROP_AUTH_PASSWORD` property when initializing the provider. *password* can't be a Microsoft Windows password.
-
-#### '*provider_string*'
-
-A provider-specific connection string that is passed in as the `DBPROP_INIT_PROVIDERSTRING` property to initialize the OLE DB provider. *provider_string* typically encapsulates all the connection information required to initialize the provider. For a list of keywords that the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Native Client OLE DB provider recognizes, see [Initialization and Authorization Properties (Native Client OLE DB Provider)](../../relational-databases/native-client-ole-db-data-source-objects/initialization-and-authorization-properties.md).
-
-<a id="table_or_view"></a>
-
-#### [ catalog. ] [ schema. ] object
-
-Remote table or view containing the data that `OPENROWSET` should read. It can be three-part-name object with the following components:
-
-- *catalog* (optional) - the name of the catalog or database in which the specified object resides.
-- *schema* (optional) - the name of the schema or object owner for the specified object.
-- *object* - the object name that uniquely identifies the object to work with.
-
-#### '*query*'
-
-A string constant sent to and executed by the provider. The local instance of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] doesn't process this query, but processes query results returned by the provider, a pass-through query. Pass-through queries are useful when used on providers that don't make available their tabular data through table names, but only through a command language. Pass-through queries are supported on the remote server, as long as the query provider supports the OLE DB Command object and its mandatory interfaces. For more information, see [SQL Server Native Client (OLE DB) Interfaces](../../relational-databases/native-client-ole-db-interfaces/sql-server-native-client-ole-db-interfaces.md).
-
-```sql
-SELECT a.*
-FROM OPENROWSET(
-    'SQLNCLI',
-    'Server=Seattle1;Trusted_Connection=yes;',
-    'SELECT TOP 10 GroupName, Name FROM AdventureWorks2022.HumanResources.Department'
-) AS a;
-```
-
 ### BULK arguments
 
 Uses the `BULK` rowset provider for `OPENROWSET` to read data from a file. In [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)], `OPENROWSET` can read from a data file without loading the data into a target table. This lets you use `OPENROWSET` with a basic `SELECT` statement.
@@ -162,6 +117,10 @@ The default for *maximum_errors* is 10.
 
 ### BULK data processing options
 
+#### DATA_SOURCE 
+
+`DATA_SOURCE` is the external location created with [CREATE EXTERNAL DATA SOURCE](../statements/create-external-data-source-transact-sql?view=azuresqldb-current&preserve-view=true).
+
 #### FIRSTROW = *first_row*
 
 Specifies the number of the first row to load. The default is 1. This indicates the first row in the specified data file. The row numbers are determined by counting the row terminators. `FIRSTROW` is 1-based.
diff --git a/docs/t-sql/functions/openrowset-transact-sql.md b/docs/t-sql/functions/openrowset-transact-sql.md
@@ -60,13 +60,13 @@ OPENROWSET
 
 #### '*provider_name*'
 
-A character string that represents the friendly name (or `PROGID`) of the data provider as specified in the registry. *provider_name* has no default value. Provider name examples are `Microsoft.Jet.OLEDB.4.0`, `SQLNCLI`, or `MSDASQL`.
+A character string that represents the friendly name (or `PROGID`) of the data provider as specified in the registry. *provider_name* has no default value. Provider name examples are `MSOLEDBSQL`, `Microsoft.Jet.OLEDB.4.0`, or `MSDASQL`.
 
 #### '*datasource*'
 
 A string constant that corresponds to a particular data source. *datasource* is the `DBPROP_INIT_DATASOURCE` property to be passed to the `IDBProperties` interface of the provider to initialize the provider. Typically, this string includes the name of the database file, the name of a database server, or a name that the provider understands for locating the database or databases.
 
-Data source can be file path `C:\SAMPLES\Northwind.mdb'` for `Microsoft.Jet.OLEDB.4.0` provider, or connection string `Server=Seattle1;Trusted_Connection=yes;` for `SQLNCLI` provider.
+Data source can be file path `C:\SAMPLES\Northwind.mdb'` for `Microsoft.Jet.OLEDB.4.0` provider, or connection string `Server=Seattle1;Trusted_Connection=yes;` for `MSOLEDBSQL` provider.
 
 #### '*user_id*'
 
@@ -127,7 +127,7 @@ For more information, see [SQL Server Native Client (OLE DB) Interfaces](../../r
 ```sql
 SELECT a.*
 FROM OPENROWSET(
-    'SQLNCLI',
+    'MSOLEDBSQL',
     'Server=Seattle1;Trusted_Connection=yes;',
     'SELECT TOP 10 GroupName, Name FROM AdventureWorks2022.HumanResources.Department'
 ) AS a;
@@ -162,12 +162,12 @@ This section provides general examples to demonstrate how to use OPENROWSET.
 
 ### A. Use OPENROWSET with SELECT and the SQL Server Native Client OLE DB Provider
 
-The following example uses the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Native Client OLE DB provider to access the `HumanResources.Department` table in the [!INCLUDE [ssSampleDBobject](../../includes/sssampledbobject-md.md)] database on the remote server `Seattle1`. (Use SQLNCLI and [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] will redirect to the latest version of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Native Client OLE DB Provider.) A `SELECT` statement is used to define the row set returned. The provider string contains the `Server` and `Trusted_Connection` keywords. These keywords are recognized by the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Native Client OLE DB provider.
+The following example uses the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Native Client OLE DB provider to access the `HumanResources.Department` table in the [!INCLUDE [ssSampleDBobject](../../includes/sssampledbobject-md.md)] database on the remote server `Seattle1`. (Use `MSOLEDBSQL` for the modern Microsoft SQL Server OLE DB Data Provider that replaced `SQLNCLI`.) A `SELECT` statement is used to define the row set returned. The provider string contains the `Server` and `Trusted_Connection` keywords. These keywords are recognized by the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Native Client OLE DB provider.
 
 ```sql
 SELECT a.*
 FROM OPENROWSET(
-    'SQLNCLI', 'Server=Seattle1;Trusted_Connection=yes;',
+    'MSOLEDBSQL', 'Server=Seattle1;Trusted_Connection=yes;',
     'SELECT GroupName, Name, DepartmentID
          FROM AdventureWorks2022.HumanResources.Department
          ORDER BY GroupName, Name'
diff --git a/docs/t-sql/statements/create-external-data-source-transact-sql.md b/docs/t-sql/statements/create-external-data-source-transact-sql.md
@@ -555,7 +555,7 @@ WITH (
 
 ### E. Create an external data source for bulk operations retrieving data from Azure Storage
 
-**Applies to:** [!INCLUDE [sssql17-md](../../includes/sssql17-md.md)] and later.
+**Applies to:** [!INCLUDE [sssql17-md](../../includes/sssql17-md.md)] and later versions.
 
 Use the following data source for bulk operations using [BULK INSERT](bulk-insert-transact-sql.md) or [OPENROWSET](../functions/openrowset-bulk-transact-sql.md). The credential must set `SHARED ACCESS SIGNATURE` as the identity, mustn't have the leading `?` in the SAS token, must have at least read permission on the file that should be loaded (for example `srt=o&sp=r`), and the expiration period should be valid (all dates are in UTC time). For more information on shared access signatures, see [Using Shared Access Signatures (SAS)](/azure/storage/common/storage-sas-overview).
 
@@ -684,7 +684,7 @@ Additional notes and guidance when setting the location:
 
 <!-- See also docs\t-sql\statements\create-external-data-source-connection-options.md -->
 
-Specified for [!INCLUDE [sssql19-md](../../includes/sssql19-md.md)] and later. Specifies additional options when connecting over `ODBC` to an external data source. To use multiple connection options, separate them by a semi-colon.
+Specified for [!INCLUDE [sssql19-md](../../includes/sssql19-md.md)] and later versions. Specifies additional options when connecting over `ODBC` to an external data source. To use multiple connection options, separate them by a semi-colon.
 
 Applies to generic `ODBC` connections, as well as built-in `ODBC` connectors for [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)], Oracle, Teradata, MongoDB, and Azure Cosmos DB API for MongoDB.
 
@@ -1138,11 +1138,11 @@ WITH (
 
 ::: moniker-end
 
-::: moniker range=">=sql-server-ver16||=sql-server-linux-ver16"
+::: moniker range="=sql-server-ver16||=sql-server-linux-ver16"
 
 ## Overview: SQL Server 2022
 
-**Applies to**: [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)]
+**Applies to**: [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)] and later versions
 
 Creates an external data source for PolyBase queries. External data sources are used to establish connectivity and support these primary use cases:
 
@@ -1154,7 +1154,7 @@ Creates an external data source for PolyBase queries. External data sources are
 
 ## <a id="syntax"></a> Syntax for SQL Server 2022
 
-## Syntax for SQL Server 2022 and later
+## Syntax for SQL Server 2022 and later versions
 
 ```syntaxsql
 CREATE EXTERNAL DATA SOURCE <data_source_name>
@@ -1226,7 +1226,7 @@ Additional notes and guidance when setting the location:
 
 <!-- See also docs\t-sql\statements\create-external-data-source-connection-options.md -->
 
-Specified for [!INCLUDE [sssql19-md](../../includes/sssql19-md.md)] and later. Specifies additional options when connecting over `ODBC` to an external data source. To use multiple connection options, separate them by a semi-colon.
+Specified for [!INCLUDE [sssql19-md](../../includes/sssql19-md.md)] and later versions. Specifies additional options when connecting over `ODBC` to an external data source. To use multiple connection options, separate them by a semi-colon.
 
 Applies to generic `ODBC` connections, as well as built-in `ODBC` connectors for [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)], Oracle, Teradata, MongoDB, and Azure Cosmos DB API for MongoDB.
 
@@ -1241,7 +1241,7 @@ Starting in [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)] Cumulative Upd
 
 #### PUSHDOWN = ON | OFF
 
-**Applies to: [!INCLUDE [sssql19-md](../../includes/sssql19-md.md)] and later.** States whether computation can be pushed down to the external data source. It is on by default.
+**Applies to: [!INCLUDE [sssql19-md](../../includes/sssql19-md.md)] and later versions.** States whether computation can be pushed down to the external data source. It is on by default.
 
 `PUSHDOWN` is supported when connecting to [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)], Oracle, Teradata, MongoDB, the Azure Cosmos DB API for MongoDB, or ODBC at the external data source level.
 
@@ -1678,7 +1678,7 @@ For a more detailed example on  how to access delta files stored on Azure Data L
 
 ### H. Create an external data source for bulk operations retrieving data from Azure Storage
 
-**Applies to:** [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)] and later.
+**Applies to:** [!INCLUDE [sssql22-md](../../includes/sssql22-md.md)] and later versions.
 
 Use the following data source for bulk operations using [BULK INSERT (Transact-SQL)](bulk-insert-transact-sql.md) or [OPENROWSET (Transact-SQL)](../functions/openrowset-bulk-transact-sql.md). The credential must set `SHARED ACCESS SIGNATURE` as the identity, mustn't have the leading `?` in the SAS token, must have at least read permission on the file that should be loaded (for example `srt=o&sp=r`), and the expiration period should be valid (all dates are in UTC time). For more information on shared access signatures, see [Using Shared Access Signatures (SAS)](/azure/storage/common/storage-sas-overview).
 
