>This smacks of the arguments on here a short while ago as to the viability of VFP in the market.
>
>I was trying to say that backend independence lets the developer agree to whatever database policies the customer may have developed at considerable cost, rather than insisting on the developer's preference. If you're saying that your customers don't have such database policies then lucky you. ;-)
>
>FWIW I think there may be some threads here from years ago about doing heavy work on the server. Plain CRUD is one thing but heavy munging can severely impact performance- unless you take it off the server and use some of the grunt of a typical Windows PC. ;-)

A lot has changed since "years ago". 64-bit Windows lets you apply tons of RAM to a server. Multi-socket mobos with 4 or more cores per socket have tons of power.

I was going to say I don't think I've ever heard of a CPU-bound SQL Server box, typically because I/O bottlenecks. But even that could change in the not too distant future, with the advent of SSDs.