On a side note, talking about only making one call to the database. You'll see in my SQL SP that I'm storing my intial query into a temporary table. What I'm doing here is telling my SP to collect all the relevant information I need in one query. I use
that data to create a temporary table variable in my SP. Then I issue queries against that temporary Table to populate my recordsets. So my Page makes a single call to my database for the information it wants for the report, and my database makes only a
single call to the remote database as well.
I just feel it's always best to keep the number of connections made to a minimum :)
Loganix77
Participant
1351 Points
412 Posts
Re: What is the better way to call multiple Stored Procedures
Apr 30, 2012 07:37 PM|LINK
On a side note, talking about only making one call to the database. You'll see in my SQL SP that I'm storing my intial query into a temporary table. What I'm doing here is telling my SP to collect all the relevant information I need in one query. I use that data to create a temporary table variable in my SP. Then I issue queries against that temporary Table to populate my recordsets. So my Page makes a single call to my database for the information it wants for the report, and my database makes only a single call to the remote database as well.
I just feel it's always best to keep the number of connections made to a minimum :)