0

If not, is there any work-around if we still want all the information to come from the same stored proc? Like wrapping these result-sets in something else(?). I have a stored proc that returns multiple result sets and it works fine. However, testing this from withing SQL Server is proving to be a challenge because of these result sets.

neuDev33
  • 1,573
  • 7
  • 41
  • 54
  • I often use multiple result sets. They allow a stored procedure to return related information in one swell foop, e.g. getting an order header and all of the line items in one request. When I do paging I'll often return one rowset that provides the first "key" element, e.g. username, for each page (implicitly providing the number of available pages) and a second rowset with the detailed items for the requested page. The "key" elements can be displayed in tooltips in the page navigation. – HABO Apr 19 '12 at 17:17
  • What is the destination for the result sets? .NET Dataset? EntityFramework? LINQ2SQL? Also, can you describe the challenges that you are encountering? – Tom Halladay May 11 '12 at 05:39

0 Answers0