Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.databases.ms-sqlserver > #698
| From | Tony C. <me@here.com> |
|---|---|
| Newsgroups | comp.databases.ms-sqlserver |
| Subject | Trying to understand 400 line stored procedure |
| Date | 2011-10-01 18:48 -0500 |
| Message-ID | <e69f875eoqplodjkvto1tcghs6rlf9beu0@4ax.com> (permalink) |
Hi, I'm trying to understand a large storedprocedure with multiple select statments like around 15 or so. I'm a little new to multiple result sets. The reader populates fields by incrementing an integer index for each field in a row not by table tnames The read uses nextresult() to move to the next restult set.... My Question is: Is the order of the resultsets in the Reader the same as the order of Select statements in the stored procedure? I suppose I should have a result set for every select statement? Just wondered how this stuff works. Thanks, Tony C.
Back to comp.databases.ms-sqlserver | Previous | Next — Next in thread | Find similar
Trying to understand 400 line stored procedure Tony C. <me@here.com> - 2011-10-01 18:48 -0500
Re: Trying to understand 400 line stored procedure Erland Sommarskog <esquel@sommarskog.se> - 2011-10-02 14:29 +0200
Re: Trying to understand 400 line stored procedure Tony C. <me@here.com> - 2011-10-02 08:29 -0500
csiph-web