Being able to service the hits on a website is a function of many things: Including:

The Box, RAM, The Pipe, Your Code, Architecture, etc.....

Lets remember that Rick worked on the surplus direct site several years ago. It is a different ball game now. SQL 7 is very fast. I have worked on an app that has a VFP front end, SQL Server 7 backend, and 500+ simultaneous users - working with tables with millions of rows of data. To find a few records, less than a second on average.. I'll take that anyday of the week...

Be careful about taking one reference and the specific circumstances that go along with it, and making that the rule that applies to all situations....

If you yourself are seeing slow performance on SQL as opposed to VFP, check the items above. Are you using SQL in an optimal manner, or, are you applying a VFP mindset to SQL? They are different animials, and need to be treated as such. If you use and implement SQL correctly, and given the proper resources, you will get blazingly fast speed, I guarantee it....



>Not according to Rick Stahl in his book. He says he has experienced up to 50% performance losses when switching from VFP local data to SQL Server on web sites. Even after bringing in outside consultants to tune SQL Server, the improvements were not signifcant. He cites examples from a huge ecommerce site that peaked at 750,000 backend hits per day.
>
>In developing C\S apps I think I see a performance diference. On some queries I can hear grinding and expereince slight hesitation, while the same queries running inside of VFP are instant. Also, browsing result sets are many times faster in VFP than in the Query Analyzer.
>
>Charlie