I'm thinking of an example master/detail page set up.

What's faster, using one stored procedure for both pages where the master does not use all of the info or creating two stored procedures, one for the master page and one for the detail.

In the first instance some info goes unused on the master page, but the query is potentially cached, or the second scenario where each procedure only returns what is needed, but there are two procedures.

Any thoughts?

I just thought of another scenario for consideration.

What about a procedure that uses of variable to decide whether to return a one of two potential recordsets, a summary or the full amount of info.

Two procedures in one.