Access (jet) vs SQL Server Express

[JBoeker]

I need to decide which database product to use for a new C# project,
Access (jet) or SQL Server Express. The project is single user; I've
used Access before in similar projects and it works OK but I'm tempted
to used SQL Express.

The only performance concern of the new project is to write a large
amount of data (3 fields) continuously during the day to a table
(approximately 300 records per second, total around 800 MB per day).
Around 2000 I looked at SQL Server and Access and Access had much lower
CPU usage (1-2% vs 10+% with occasional spikes to 20%).

I'm interested in any advice, feedback.

Thanks,

Jeff

 

[W.G. Ryan - MVP]

Sql Server express gives you a lot that access doesn't, but you may not
necessarily need it all. I'm 100% biased in this respect though and shun
access like it's ebola - so consider my admitted bias when reading my
response.

Express gives you a lot better security features and manageability.

Backing up and restoring is greatly enhanced.

Upgrading to full Sql Server is more straightforward.
If you need replication, it's going to be a lot easier.
You can use Stored procs, triggers etc.
You can use T-Sql.

-----
Since it's a single user app, a lot of that's off the table. You probably
won't be upgrading to Sql Server enterprise edition any time soon b/c the
app's single user needs load balancing or the like. Security management is
not that much of an issue either in a on person environment. Stored Procs
and T-Sql - depends on your app, may or may not be a big deal.
Backup/Recovery - again, it depends on the app and the user.

So as much as I like ragging on Access, it's probably every bit as good of a
choice as Express is based on your requirements.

Cheers,

Bill

 

[Paul Clement]

On 22 May 2006 11:44:58 -0700, (e-mail address removed) wrote:

¤ I need to decide which database product to use for a new C# project,
¤ Access (jet) or SQL Server Express. The project is single user; I've
¤ used Access before in similar projects and it works OK but I'm tempted
¤ to used SQL Express.
¤
¤ The only performance concern of the new project is to write a large
¤ amount of data (3 fields) continuously during the day to a table
¤ (approximately 300 records per second, total around 800 MB per day).
¤ Around 2000 I looked at SQL Server and Access and Access had much lower
¤ CPU usage (1-2% vs 10+% with occasional spikes to 20%).
¤
¤ I'm interested in any advice, feedback.

I would give the performance and portability edge to Access.

Access has a 2 GB size limit. SQL Server Express is 4 GB and is probably better suited to handle
large amounts of data. If you're approaching either of these numbers you will need to consider a
more robust database server package.

SQL Server Express requires less maintenance. You need to compact an Access database on at least a
weekly basis in order to keep it in top working condition. An Access database is more prone to
corruption, although it's very reliable in a single user/locally installed environment.


Paul
~~~~
Microsoft MVP (Visual Basic)

 

[Robbe Morris [C# MVP]]

OleDb provider in .net is extremely slow with ADO.NET
and Access. At least it was with .net 1.1