| title | Table-Valued Parameters (OLE DB) | Microsoft Docs | ||
|---|---|---|---|
| ms.custom | |||
| ms.date | 03/14/2017 | ||
| ms.prod | sql | ||
| ms.prod_service | database-engine, sql-database, sql-data-warehouse, pdw | ||
| ms.reviewer | |||
| ms.technology | native-client | ||
| ms.topic | reference | ||
| helpviewer_keywords |
|
||
| ms.assetid | 4298b73d-615b-4d28-9843-03b4d5fc489e | ||
| author | markingmyname | ||
| ms.author | maghan | ||
| monikerRange | >=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017||=azuresqldb-mi-current |
[!INCLUDEappliesto-ss-asdb-asdw-pdw-md]
This section describes support for table-valued parameters in [!INCLUDEssNoVersion] Native Client OLE DB Provider. For additional overview information, see Table-Valued Parameters (SQL Server Native Client). For a sample, see Use Table-Valued Parameters (OLE DB).
Currently, you can send multirow data to the server as parameters to a procedure with parameter sets (the DBPARAMS parameter in ICommand::Execute). With parameter sets, every element of the set has to be sent in a separate remote procedure call (RPC) request to the server. Table-valued parameters provide similar functionality, but there is better integration with the server. This reduces the number of RPC requests and enables set-based operations on the server.
Table-value parameters are supported in [!INCLUDEssNoVersion] Native Client OLE DB Provider as OLE DB Rowset objects. Any Rowset object could be provided by the consumer (that is, the client application using [!INCLUDEssNoVersion] Native Client OLE DB Provider) as a placeholder for table-valued parameter parameters. Table-valued parameters are treated like other [!INCLUDEssNoVersion] parameter types. The [!INCLUDEssNoVersion] Native Client OLE DB Provider provides creation, discovery, specification, binding and schema interfaces.
SQL Server Native Client (OLE DB)
Use Table-Valued Parameters (OLE DB)