Why choose SQL Express over Access?

[raibeart]

It is like comparing a VW bug with a Mercedes.

JET has corruption problems.
It is not meant for use over the internet.
It is not meant for more that 3 or 4 users.
No clear migration path to higher end DBs.
Limited capacity.
Slow.
File system based technology.
File copy of empty MDB file for data to specific directory structure.
Poor security model.

SQL Express is meant for up to 10 users.
It is faster.
It gives you a full migration path to full SQL Server.
With the new release you have admin tools.
Multiple instances can be deployed for individual applications.
Server based technology.
Can be installed with a tool like Win Batch.
Specific DBs created after install as part of the install script using
Win Batch.
SQL Server security model.

Also, when will everyone get it through their heads. JET is a database
engine that Access uses, just like it uses SQL Server. Access is a GUI
and programming environment. Asking SQL Express or Access is like
asking VB or SQL Express, it is like apples and oranges.

[Paul Clement]

On 1 Jun 2006 05:45:15 -0700, "raibeart" <ra******@gmail.com> wrote:

¤ It is like comparing a VW bug with a Mercedes.
¤

Not really. They both have advantages over the other depending upon the
environment.

¤ JET has corruption problems.

If not maintained properly yes this can be problem.

¤ It is not meant for use over the internet.

Probably not, but certainly can be in environments that are not high volume.

¤ It is not meant for more that 3 or 4 users.

Nah, concurrent usage is a little better than that.

¤ No clear migration path to higher end DBs.

You can migrate to SQL Server. Access has an upsizing wizard to do so.

¤ Limited capacity.

Yeah, 2GB. SQL Express is also limited to 4GB.

¤ Slow.

Not inherently no. OLEDB performance isn't great, but DAO will beat the pants
off of SQL Server.

¤ File system based technology.

Which makes it portable, with limited database engine technology.

¤ File copy of empty MDB file for data to specific directory structure.

?

¤ Poor security model.

Yeah, certainly not the best.

¤ SQL Express is meant for up to 10 users.

And probably more reliable than Access.

¤ It is faster.

Not from my experience.

¤ It gives you a full migration path to full SQL Server.
¤ With the new release you have admin tools.

Yes, but the tools (especially end user) from Access are far superior.

¤ Multiple instances can be deployed for individual applications.
¤ Server based technology.

Which means it's less portable, but significantly more flexible in a multi-user
environment.

¤ Can be installed with a tool like Win Batch.

I'm assuming you're referring to the files and not SQL Express itself which
requires some configuration.

¤ Specific DBs created after install as part of the install script using
¤ Win Batch.
¤ SQL Server security model.

Yup, much better here.

¤ Also, when will everyone get it through their heads. JET is a database
¤ engine that Access uses, just like it uses SQL Server. Access is a GUI
¤ and programming environment. Asking SQL Express or Access is like
¤ asking VB or SQL Express, it is like apples and oranges.

Interesting points.

In addition, Access was designed to be more of an end-user self-contained and
portable application based, passive data store while SQL Server Express is still
more suited for developers looking for a more robust data store with built-in
dynamic capabilities that with a little effort can also be used in a local
application database scenario.

Paul
~~~~
Microsoft MVP (Visual Basic)

[Dennis]

What's your opinion of "MySQL"?
--
Dennis in Houston
"Paul Clement" wrote:

On 1 Jun 2006 05:45:15 -0700, "raibeart" <ra******@gmail.com> wrote:

¤ It is like comparing a VW bug with a Mercedes.
¤

Not really. They both have advantages over the other depending upon the
environment.

¤ JET has corruption problems.

If not maintained properly yes this can be problem.

¤ It is not meant for use over the internet.

Probably not, but certainly can be in environments that are not high volume.

¤ It is not meant for more that 3 or 4 users.

Nah, concurrent usage is a little better than that.

¤ No clear migration path to higher end DBs.

You can migrate to SQL Server. Access has an upsizing wizard to do so.

¤ Limited capacity.

Yeah, 2GB. SQL Express is also limited to 4GB.

¤ Slow.

Not inherently no. OLEDB performance isn't great, but DAO will beat the pants
off of SQL Server.

¤ File system based technology.

Which makes it portable, with limited database engine technology.

¤ File copy of empty MDB file for data to specific directory structure.

?

¤ Poor security model.

Yeah, certainly not the best.

¤ SQL Express is meant for up to 10 users.

And probably more reliable than Access.

¤ It is faster.

Not from my experience.

¤ It gives you a full migration path to full SQL Server.
¤ With the new release you have admin tools.

Yes, but the tools (especially end user) from Access are far superior.

¤ Multiple instances can be deployed for individual applications.
¤ Server based technology.

Which means it's less portable, but significantly more flexible in a multi-user
environment.

¤ Can be installed with a tool like Win Batch.

I'm assuming you're referring to the files and not SQL Express itself which
requires some configuration.

¤ Specific DBs created after install as part of the install script using
¤ Win Batch.
¤ SQL Server security model.

Yup, much better here.

¤ Also, when will everyone get it through their heads. JET is a database
¤ engine that Access uses, just like it uses SQL Server. Access is a GUI
¤ and programming environment. Asking SQL Express or Access is like
¤ asking VB or SQL Express, it is like apples and oranges.

Interesting points.

In addition, Access was designed to be more of an end-user self-contained and
portable application based, passive data store while SQL Server Express is still
more suited for developers looking for a more robust data store with built-in
dynamic capabilities that with a little effort can also be used in a local
application database scenario.

Paul
~~~~
Microsoft MVP (Visual Basic)

[Paul Clement]

On Fri, 2 Jun 2006 16:57:02 -0700, Dennis <De****@discussions.microsoft.com> wrote:

¤ What's your opinion of "MySQL"?

Actually I haven't used it so I can't offer much of an opinion. But based upon the little research
I've done I would say it's a poor man's SQL Server. That doesn't mean I think it's bad, just that it
isn't comparable with respect to features.
Paul
~~~~
Microsoft MVP (Visual Basic)

[Dennis]

Thanks for you input. I have used it in one web application and it worked ok
but does have limitations including documentation. However, when I tried to
put it on my actual web site running under my service provider, it was very
difficult to get it uploaded...not nearly so easy as an SQL or Access
database. I never did get it uploaded.
--
Dennis in Houston
"Paul Clement" wrote:

On Fri, 2 Jun 2006 16:57:02 -0700, Dennis <De****@discussions.microsoft.com> wrote:

¤ What's your opinion of "MySQL"?

Actually I haven't used it so I can't offer much of an opinion. But based upon the little research
I've done I would say it's a poor man's SQL Server. That doesn't mean I think it's bad, just that it
isn't comparable with respect to features.
Paul
~~~~
Microsoft MVP (Visual Basic)