| title | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.topic | helpviewer_keywords | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
Create rowset with ICommand::Execute (Native Client OLE DB provider) |
Create rowset with ICommand::Execute (Native Client OLE DB provider) |
markingmyname |
maghan |
03/14/2017 |
sql |
native-client |
reference |
|
[!INCLUDESQL Server Azure SQL Database Synapse Analytics PDW]
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 [!INCLUDEssNoVersion] Native Client OLE DB provider 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 [!INCLUDEssNoVersion] Native Client OLE DB provider 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.