Access or SQlServerExpress

[bob]

Hi,
OK, it is off topic but I am looking for c# developer feedback.
New Windows app project totally selfcontained.
Will need to handle BLOBs (pictures)
Useful life about 5 years then into the bin.
Doesn't justify a heavy weight Database engine.
Remote deployment. (O'seas)
I was originally going to use Access but then thought of SqlServer
2005 Express.
What does the panel think?
thanks
Bob

 

[Arne Vajhøj]

OK, it is off topic but I am looking for c# developer feedback.
New Windows app project totally selfcontained.
Will need to handle BLOBs (pictures)
Useful life about 5 years then into the bin.
Doesn't justify a heavy weight Database engine.
Remote deployment. (O'seas)
I was originally going to use Access but then thought of SqlServer
2005 Express.
What does the panel think?

Only 1 user of each database => embedded database and I will
suggest SQLServer Compact Edition instead of Access Jet.

More than 1 user of each database => insist on getting
SQLServer Express installed.

Arne

 

[sloan]

I'd try for Express as hard as you can.

However, there is a way to develop your code "smart" as well.

http://sholliday.spaces.live.com/Blog/cns!A68482B9628A842A!176.entry

The Compaq Edition is an option.

Others will chime in with a few other options as well.

........

Either way if you check the example above, you can develop code which will
protect yourself for a possibly db switch.

 

[Larry Smith]

Hi,

OK, it is off topic but I am looking for c# developer feedback.
New Windows app project totally selfcontained.
Will need to handle BLOBs (pictures)
Useful life about 5 years then into the bin.
Doesn't justify a heavy weight Database engine.
Remote deployment. (O'seas)
I was originally going to use Access but then thought of SqlServer
2005 Express.
What does the panel think?
thanks

I wouldn't make any decision just yet. Just code it generically and plug
your DB in later. You can then determine which is best based on your
evoloving requirements. You might even want to use some other DB like MySQL
or maybe even XML if the situation warrants - you then wouldn't need any
RDBMS at all but would still be able to use the limited RDBMS capabilities
of the native ADO.NET classes.

 

[Simon Tamman]

If we're talking 1 user then i'd say Sqlite is better than SqlCe. It also has
an ADO.NET wrapper available (on source forge) for convienience and as of 3.0
can store blobs that are > 1 mb.

 

[bob]

Hi to 'the panel',
Thanks for your replies.
What I am hearing is Generic Data Transfer Layer and SLQ Server
Express preferred over Access.
Must admit I had lost sight of writing a database agnostic layer.
Thanks for timely reminder.
Hadn't considered Compact Edition, always regarded it as designed for
Handhelds. It would be unsuitable in this instance as I expect
multiple users but an interesting idea nonetheless.
regards
Bob