Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Future as a FoxPro Developer
Message
From
01/07/2004 11:44:46
John Baird
Coatesville, Pennsylvania, United States
 
 
To
01/07/2004 11:33:19
Walter Meester
HoogkarspelNetherlands
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00918302
Message ID:
00919665
Views:
37
Then you need to rethink your data model. And application data processing is what the backend is for....



>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,
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform