or you can call all five procs in one batch.
one trip is better, you just get mulitiple result sets back, if the batch
calls mltiple (or the sp calls multiple).
-- bruce (sqlwork.com)
On Feb 11, 3:49 pm, bruce barker
<brucebar...@discussions.microsoft.com> wrote:
> or you can call all five procs in one batch.
>
> one trip is better, you just get mulitiple result sets back, if the batch
> calls mltiple (or the sp calls multiple).
>
> -- bruce (sqlwork.com)
OK, to call all five procs in one batch, we need to create another
stored procedure that calls these 5 stored procedures, right? Please
kindly let me know, I have always been wondering what people mean by
"one batch".
Thanks a lot!