Skip to content

Latest commit

 

History

History
29 lines (24 loc) · 2.03 KB

File metadata and controls

29 lines (24 loc) · 2.03 KB
title Creating Rowsets with ICommand::Execute | Microsoft Docs
ms.custom
ms.date 04/27/2017
ms.prod sql-server-2014
ms.reviewer
ms.technology native-client
ms.topic reference
helpviewer_keywords
rowsets [OLE DB], creating
SQL Server Native Client OLE DB provider, rowsets
OLE DB rowsets, creating
Execute method
ms.assetid 9b530b7d-8165-49d4-a978-5ced17c6705e
author MightyPen
ms.author genemi
manager craigg

Creating Rowsets with ICommand::Execute

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.

See Also

Rowsets