K
Kathy
When should you use Access and when should you use SQL server
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
L
Larry Daugherty
Hi Kathy,
There is a bunch of confusion engendered by MS that developers overcome in
time and then forgot that there was a time when they didn't know: While we
always say that "Access is the Relational Database product from Microsoft".
The truth is that Access is a bunch of development tools and user interface
components that are packaged with the JET relational database management
system by default. And, for a few versions now, MSDE, which is a watered
down version of SQL Server, is also included.
If your application is to be all or any of the following: on line,
real-time, mission critical; then SQL Server or Oracle or DB2 may be the
way to go. If your data tables approach the JET limit of 2G then you may
want to move to MSDE or SQL Server.
If your world won't come to an end with an occasional crash of your
application then I'd recommend sticking with the default Access & JET
configuration. If you don't explicitly choose differently that's what you
get. That's the flavor of most Access applications. The most common cause
of crashes and file corruption is power failures or users simply turning off
their system while in the application rather than making an orderly exit
from the application.
HTH
There is a bunch of confusion engendered by MS that developers overcome in
time and then forgot that there was a time when they didn't know: While we
always say that "Access is the Relational Database product from Microsoft".
The truth is that Access is a bunch of development tools and user interface
components that are packaged with the JET relational database management
system by default. And, for a few versions now, MSDE, which is a watered
down version of SQL Server, is also included.
If your application is to be all or any of the following: on line,
real-time, mission critical; then SQL Server or Oracle or DB2 may be the
way to go. If your data tables approach the JET limit of 2G then you may
want to move to MSDE or SQL Server.
If your world won't come to an end with an occasional crash of your
application then I'd recommend sticking with the default Access & JET
configuration. If you don't explicitly choose differently that's what you
get. That's the flavor of most Access applications. The most common cause
of crashes and file corruption is power failures or users simply turning off
their system while in the application rather than making an orderly exit
from the application.
HTH
M
margaret bartley
Kathy said:When should you use Access and when should you use SQL server
In addition to Larry Daugherty's reply, another consideration is your level
of IT support.
SQL has a lot more overhead, costs a lot more money, requires a much higher
level of IT support.
There are millions of businesses out there using Access to keep track of
core business processes, that are being managed by a support staffer
(department secretary, analyst, etc). That could not happen with SQL
server.