Jet vs. SQL

[Guest]

Hello Everybody.

Can someone tell me, what the critical issues are that would necessitate a
switch from the Jet Database Engine to SQL Server? Is it the number of
records? If so, at what number does the Jet Engine begin to show strain? Is
there a maximum number in SQL also? Or would I rather have to look at the
number of queries per second to decide? Or is it perhaps something else
alltogether (memory, storage, etc.)?

The reason I am asking is that we need to set up a database that could
expand to lots of records (>100,000). Will the Jet Engine (Access) be able to
handle this or will it break/slow down?

mike

 

[Douglas J. Steele]

~100,000 records is still fairly small for an Access database, so I wouldn't
use that as a criterion.

To me, major reasons for SQL Server are to handle users with a distributed
geography (Access definitely doesn't play well across a WAN), requirement
for increased security (no file-based application offers particularly good
security), need for a robust infrastructure (SQL Server logs its
transactions, can be backed up while in use and many other such features)
and large number of users (especially a large number of users updating
concurrently)