Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
VB, C#, and VFP data handling examples
Message
De
29/04/2007 02:35:44
 
 
À
27/04/2007 20:30:50
John Baird
Coatesville, Pennsylvanie, États-Unis
Information générale
Forum:
Visual FoxPro
Catégorie:
Visual FoxPro et .NET
Divers
Thread ID:
01215120
Message ID:
01220864
Vues:
34
Well, as another professional programmer, I can say that relying on stored procedures for all processing is not the way to go. What has not been said is that .Netters rely on stored procedures because there are no other viable alternatives at this time.

As a professional programmer, I can attest that, on a recent project, we were initially using SPs called from a VFP middle tier COM server (via pass through) to generate XML for some extremely large and complex reports from an SQL server with tables in the millions of records. The data was highly normalized and the SELECTs were extremely complex. The performance was terrible and we worked with a DBA and a Microsoft SQL Server consultant (who was actually hired for another project) to make sure our SPs were the best they could be - they were. Then we decided to dump the SPs and create a series of more simple SELECTs (using pass through) resulting in intermediate data sets which were then used by VFP to create the final SELECTs. Performance increased by more than 20 times.

Futhermore, it is now common knowlege that most business rules should not reside in SPs. Too many round trips to the server, not to mention servers getting bogged down with processes that could be executed on another tier. Again, .Netters have to rely more on SPs because there are no alternatives at this time. I say "at this time" because Microsoft is finally doing something about it.

So it looks like you may have to change your way of thinking and move on like a professional programmer. And, yes, I am singling you out.


>Well as a professional programmer I'm sure that you want to take advantage of the strengths of the new language and not do things the old way. When I stopped programming in VFP, I left VFP techniques, the VFP toolkit for .net and all other such thoghts behind. I wanted to learn .Net not .Net with a vfp twist. The move to .Net will require a shift in thinking about how data is handled. That's why most of the .netters here are espousing stored procedures. Most of the processing should take place on the server and almost none on the client.
>
>So you can continue to think about .Net in VFP Terms or you can move on like a professional programmer and think about .Net in .Net terms.
>
>My usage of YOU in the above is not meant to single you out. It is a generic usage.
- Jeff
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform