I posted this in the Database development forum, but, got to thinking that the folks here might actually have a better handle on this.

I've been charged with converting a number of stored procedure (SP) type SQL extractions to run at the client instead of at the server.

These SP's run several dozen separate SQL statements, creating a number of temp tables that are later joined/updated/combined to yield a final dataset that's applied to an existing Crystal report.

I'm looking for a way to either, direct the SP's to run on the client instead of on the server (probably not possible), or, a way to emulate the temp table and joins/updates/combines with datatables within a strongly typed dataset.

Any ideas? I know that using stored procedures is really the 'recommended' best practice, the issue here is the processor burden on the server. Running the existing stored procedures bogs the server such that other applications can become erratic.

Thanks,

-Bill