Database with .NET

[michael_hk]

I just think that would be good for everyone that posts like the one from michael_hk

 

simply didn't had a point... ;)

Alex

 

I think no one will deny Access is a weak database, how many simultaneous user support can it support?? But I DO agree Access is good for some situation, like for a small app.

 

I am just surprised by the fact that many are using Access, NOT having anything against Access.

[Joe Mamma]

I think no one will deny Access is a weak database, how many simultaneous user support can it support?? But I DO agree Access is good for some situation, like for a small app.

 

I am just surprised by the fact that many are using Access, NOT having anything against Access.

Hybridization!!!

 

Jet (or BDE in Borland situations) is great for doing local processing and configuration management. Server for the enterprise wide portion of the app.

 

Now that JET can handle DDL outside of Access proper (MDAC 2.7 and above) this approach is fantastic.

 

I mean, christ, MS-SQL server uses the jet engine to do somethings.

At least that what I figure geven I couldnt delete some JET*.tmp files without shutting down my SQL server process.

[samsmithnz]

Ok, I'm jumping into this conversation a year late... BUT. the main disadvantage with access as I see it, is that the connection initalization is too slow. Especially with the way Microsoft promotes only having a connection open for as long as you need it, an application using an Access database is noticably slower opening each database connection.

[Nerseus]

@samsmithnz:

MS recommends only keeping a connection open as long as you need it for multi-user applications, mostly those accessed through a common server - usually a webserver. MS Access is primarly single user. I would never open/close a connection on every query to Access. If you have a multi-user application, MS now recommends MSDE over Access.

 

-ner

[AlexCode]

"... the connection initialization is too slow"

We can use connection pooling.

 

"...MS now recommends MSDE over Access"

The deployment is the big issue. We can't compare the two on this field.

We sell about 6 apps on top of an Access DB... we just have to add the .mdb file to the installation...

 

"...MS Access is primarily single user."

Agree and disagree. I believe it was meant for a single user access but it behaves very well on a multi-user scenario. The problem isn't how many people access the mdb file, it's:

- How many field changing queries (Updates, Inserts & Deletes)

- The amount of records processed per query

- The amount or existence of concurrency

- The predicted DB growth

- The predicted DB Clients growth

 

For me, these are the factors that make me choose between MS Access and a SQL Server Engine (MSSQL Server 2000, MySQL or Oracle).

 

 

Alex :p

[kurf]

I currently use SQL Server 2005 and support it fully and choose no other :D