SQL server works completely differently from FoxPro. For Sql Server the performance even on the same system would heavily depend on the isolation level you use, concurrent access and memory usage. I've consulted on SQL server databases projects in the close to a TB database size range where developers were thinking that performance optimization means creating the right indexes, but totally ignored how SQL server locking works, how transactions work, how memory can be utilized, etc.
It does make a big difference, if the database engine knows which parts of a file have changed (SQL Server) vs. it can only tell if a file has changed, if at all (VFP). BTW, what exactly is "glTable600"? -- Christof > On 24. Oct 2020, at 17:25, Stephen Russell <srussell...@gmail.com> wrote: > > I just did a count(*) from one of our biggest tables. It took 2 min to > load it into memory the first time. > SELECT count(*) cnt > FROM [erplndb].[dbo].[glTable600] > > cnt > 138,371,855 > > The second time I run this it only takes .03 seconds. The size of the > table and index is a mere 364 gigs today. > --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/daf37e96-609c-4e59-a4bd-63ab36064...@wollenhaupt.org ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
