| title | Create rowset with ICommand::Execute (OLE DB driver) | ||||
|---|---|---|---|---|---|
| description | Learn about creating rowsets with ICommand::Execute in OLE DB Driver for SQL Server. The properties that you want in the rowset can constrain the command text. | ||||
| author | David-Engel | ||||
| ms.author | davidengel | ||||
| ms.date | 06/14/2018 | ||||
| ms.service | sql | ||||
| ms.subservice | connectivity | ||||
| ms.topic | reference | ||||
| ms.custom |
|
||||
| helpviewer_keywords |
|
[!INCLUDE SQL Server Azure SQL Database Azure SQL Managed Instance Azure Synapse Analytics PDW FabricSQLDB]
[!INCLUDEDriver_OLEDB_Download]
For rowsets created by using the ICommand::Execute method, the properties that you want in the resulting rowset can constrain the text of the command. This is especially critical for consumers that support dynamic command text.
The OLE DB Driver for SQL Server cannot use [!INCLUDEmsCoName] [!INCLUDEssNoVersion] cursors to support the multiple-rowset results generated by many commands. If a consumer requests a rowset requiring [!INCLUDEssNoVersion] cursor support, an error occurs if the command text generates more than a single rowset as its result. For more information, see Commands Generating Multiple-Rowset Results.
Scrollable OLE DB Driver for SQL Server rowsets are supported by [!INCLUDEssNoVersion] cursors. [!INCLUDEssNoVersion] imposes limitations on cursors that are sensitive to changes made by other users of the database. Specifically, the rows in some cursors cannot be ordered, and trying to create a rowset by using a command that contains a SQL ORDER BY clause can fail. For more information, see Rowsets and SQL Server Cursors.