Hi!
How MS Access compares with SQL, Oracle and SAP. One in my workplace
told me Access is not suitable for large companies using their own
servers, intranet and requires multiuser capability. Is it true? Also if
I learn Access well will it help learning SQL database quickly?
Thanks.
This is not an apples to apples comparison. Those other products you
mention are database engines only. Access is a database application
development platform used to create a user interface to a database.
By default Access is set up to use the built-in Jet database engine, but
you can also use Access to build applications that use any of the
aforementioned server database engines as well.
So the *proper* question is "How does *Jet* compare to SQL, Oracle,
etc..?". Access as the tool to build the interface is NOT part of that
question. For building the interface you would be asking "How does
Access compare to VB, dot-net, Java, etc..?".
Now, concerning the question "How does Jet compare to..." it is true that
as database size, number of concurrent users, and security requirements
get above a certain threshold then Jet is not a good choice and a server
database should be used. As it pertains to Multi-User on a local LAN the
limits for Jet depend greatly on the database and the application used to
interface with it. Some can accommodate 50 to 100 users without a
problem while others could struggle with more than just a handful of
users.
It is certainly not true that you cannot use an Access/Jet solution in a
multi-user scenario. One does have to know what they are doing though.
In a single user app you can get away with a ton of sloppy/incorrect
design aspects, but these cause problems when multiple users are
involved.
That is how Access/Jet got its bad reputation for multi-user situations.
A novice builds an app mostly using the wizards and over time tries to
make a whole department or company run off of it. That is a recipe for
failure. A competent developer though could build that same Access/Jet
app with no problems at all until/unless the requirements really do
exceed what is practical for a Jet database. At that point the Access
interface could still be used after migrating the database to a more
robust server engine.