[dba-VB] SCRUM: Northwind.NET v.1.1 (Alpha) with MS Access Backend published

Another option is SQLite.  I'd go with that rather than CE.

Not for multi-user applications, but if you ned a small, lightweight in-process SQL data 
engine for a single user application it's well worth looking at.  Just a single small DLL to 
distribute with your application ( < 450KB).
 
There are .Net wrappers available which make it very simple to use.

 
On 26 Apr 2009 at 23:02, Mark Breen wrote:

> Hi All,
> I have been seeing SQL Server compact edition for a while now, but I have
> not read up about it yet.  If it is so light as Gustav just outlined then I
> really should study it.  It sounds just what the doctor ordered, I have
> always thought, since MSDE 1.0 was launched, that it was too heavy.
> 
> However, I re-call struggling with a machine that did not have Jet 3.51, and
> I suppose that installing / using SQL Server CE may also have issues.
> 
> What the pros / cons to building an XML only BE?
> 
> As I write this, I see the following potential list of BE's
> 
> XML only - Simplest Implementation at installation time.
> SQL Server CE - Not Sure as have to study
> Jet - Ideal for low volume of data and low numbers of users.
> SQL Server Express - where mid sized data, mid users and hand installation
> is possible if required.
> SQL Server Standard -where mid sized data, mid users and hand installation
> is possible if required and cost is not an issue
> mySQL - high data size and licencing cost is an issue
> Oracle - Just because it is there.
> 
> So where does that leave the discussion on what to do next?
> 
> I am off to read up on SQL Sever CE
> 
> Mark
> 
> 
> 
> 
> 
> 2009/4/26 Gustav Brock <Gustav at cactus.dk>
> 
> > Hi all
> >
> > It is my impression that - in the mind of MS - a downgrade from SQL Server
> > 200x (server-based) should be the SQL Server Compact Edition which is
> > file-based as Access/JET is except that it is local and not shareable but is
> > deployable via Click-Once.
> > Next level below is pure XML.
> >
> > Using Access/JET - or MySQL or any other db - is simply another "business".
> >
> > /gustav
> > t
> >
> > >>> max.wanadoo at gmail.com 26-04-2009 19:26 >>>
> > Arthur:
> > Because...
> > 1. I don't know how to do this.
> > 2. I don't see any benefits other than more pain.
> > 3. I don't see any DAO.Properties on the SQL tables.
> >
> > Inertia.   Perhaps.
> >
> > Max
> >
> >
> > -----Original Message-----
> > From: dba-vb-bounces at databaseadvisors.com
> > [mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller
> > Sent: 26 April 2009 15:39
> > To: Salakhetdinov Shamil; Discussion concerning Visual Basic and related
> > programming issues.
> > Subject: Re: [dba-VB] SCRUM: Northwind.NET v.1.1 (Alpha) with MS Access
> > Backend published
> >
> > Shamil,
> >
> > It is not interesting to me, personally. All my database activity occurs in
> > SQL Server and MySQL. The concept of an Access BE is for me so 20th century
> > LOL. However, I realize that not everyone agrees and that some folks might
> > like an Access BE. (Although given that SQL Express is free, I frankly
> > don't
> > understand this, other than the force of inertia.)
> >
> > Arthur
> >
> >
> >
> > _______________________________________________
> > dba-VB mailing list
> > dba-VB at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/dba-vb
> > http://www.databaseadvisors.com
> >
> >
> _______________________________________________
> dba-VB mailing list
> dba-VB at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-vb
> http://www.databaseadvisors.com
>