John,

>Then you need to rethink your data model.

I don't think you read it carefully:
The resultset of the data munging routine is way larger than the summ of the size of tables involved in the datasession.

>And application data processing is what the backend is for....

A big, BIG mistake, too often made. There should be no application depended data processing logic on the database backend. I admit you cannot alway avoid it, but it should be a goal. The whole idea of middle tiers is based on this idea.

Walter,



>>John,
>>
>>>All of that processing can be as easily done in the sproc using cursors and temptables. You then return the completed dataset to the program. Again, your standard doesn't fly.
>>
>>I know it can, but just give me the code and compare its performance and compactness.
>>
>>When talking about the appointment cursor, well you'd better look twice. It is not that easy to solve in SQL server. And above all, you're doing application depended processing on a server. Something that really does not belong there. These type of processing can draw your whole server down as it might consume way too much resource, esspecially when the number of users grow.
>>
>>And the point here is that the returned resultset probably is way larger than the summ of all tablessize in this example, so also stressing networkbandwidth
>>
>>Walter,