| title | Creating Rowsets with ICommand::Execute | 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 | 9b530b7d-8165-49d4-a978-5ced17c6705e | ||||
| 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]
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 an SQL ORDER BY clause can fail. For more information, see Rowsets and SQL Server Cursors.