<{{Subtitle_Weight}} class="prominent-subhead {{Show_Subtitle}}"> {{Header_Subtitle}}

K2 SQL Server Broker: Stored Proc Requirements

~~repeating-content.html~~
LEGACY/ARCHIVED CONTENT
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.

When using the K2 blackpearl OOTB SQL Server Service Broker (Broker) to expose Stored Procedures (SProcs) you will sometimes find methods based on these stored procedures that do not expose the expected properties of the returned datasets. These cases are due to the dynamic nature of the result set schema, which prevents it from being properly mapped to the SmartObject (SmO) properties.

To get the column information, the stored procedure is executed in ADO.NET with System.Data.CommandBehavior.SchemaOnly. This is the same as executing it with SET FMTONLY option. Thus, to ensure that your SProcs results set will be properly exposed the SProc needs to be able to execute without error when SQL’s SET FMTONLY option is set to ON.

Download the PDF in the right-hand menu to view the full article.