Why choose SQL Express over Access?

  • Thread starter Thread starter ljh
  • Start date Start date
There is indeed a mathematical principal behind all that goes on in this
world, Neo. ;-)

- Sahil Malik
http://www.winsmarts.com
http://blah.winsmarts.com




Bob said:
Sahil --

After writing my last reply to your message, I still can't believe that
I had the helicopter dream last night. I rode in a helicopter once in
my life, and that was about 30 years ago. I have NEVER (that I can
remember) ever had a helicopter dream -- until last night. I haven't
checked the time of your message, but I suspect that my dream must have
occurred after you wrote me your message. I really wonder if there is
some "medium" out there that carries brain waves around, or something,
whereby my subconcious received some glint of your thought before I
actually read it. WOW!

btw, what does "MSFT" stand for?

Thanks,

With the pace at which MSFT is releasing new stuff, I suggest getting
over
the concept of climbing mountains and investing in a helicopter. :)

- Sahil Malik [MVP]
http://blah.winsmarts.com





The best reason for guys like me: I ALREADY KNOW HOW TO USE ACCESS!!!

I've just obtained vb.net express and I'm having enough trouble
learning how to use it (and un-learning VB6). Right now, I don't want
to climb another mountain while I'm climbing this one.


Sahil Malik [MVP C#] wrote:
Short incomplete list of reasons -

- SQL Express (or SQL Server in general) will scale better to multiple
users.
- It will give you a "way out" when your DB exceeds 4GB
- It will be easier to maintain from a DBA point of view (centralized
backups *.*)
- It will give you a much richer feature set - notification, SQLCLR,
better
T-SQL*.*
- It will give you better performance (No OleDb necessary)
- You won't have to compact it as often
- Better support for data types/indexes etc. etc.
- Other reasons.

The only advantage Access gives you is "File based deployment". And
frankly
SQL Anywhere (or was it everywhere - I loose track in all these name
changes) should be a better choice for desktop-ish applications
anyway.

- Sahil Malik
http://www.winsmarts.com


Why would you choose SQL Express (which requires an installed
application
to work) over the simplicity of an Access database which has no
dependencies?
Click to expand...
Click to expand...
Click to expand...
 
Are there any comparisons/tests for concurrent usage that show SQLite
to behave better than Access? I haven't looked at Access as a database
for a web app since the ASP classic days, and I like what SQLite has to
offer, but want to be sure I won't end up with the same problems that
Access is notorious for. One thing that Access has in its favor is that
the DB can be copied to a client's PC and you can be sure they can
check out the contents with Office.
 
Are there any comparisons/tests for concurrent usage that show SQLite
to behave better than Access? I haven't looked at Access as a database
for a web app since the ASP classic days, and I like what SQLite has to
offer, but want to be sure I won't end up with the same problems that
Access is notorious for. One thing that Access has in its favor is that
the DB can be copied to a client's PC and you can be sure they can
check out the contents with Office.
Click to expand...

There are an equally large number of people that consider that "feature" a
showstopper and a nightmare :)

I have a few SQLite vs. Access/Firebird/Vista/Sql Express benchmarks here:
http://sqlite.phxsoftware.com/forums/622/ShowPost.aspx

As for the rest ... you'll find a features overview (as it pertains to the
ADO.NET 2.0 provider) at the main site:
http://sqlite.phxsoftware.com

Robert
 
Back
Top