Re: Choosing a Windows Database
From: Greg Low [MVP] (greglow_at_lowell.com.au)
Date: 01/05/05
- Next message: BWOlson: "Re: Visual Basic 6.0 and Access 2000"
- Previous message: Ralph: "Re: Choosing a Windows Database"
- In reply to: Ralph: "Re: Choosing a Windows Database"
- Next in thread: Mitchell Vincent: "Re: Choosing a Windows Database"
- Reply: Mitchell Vincent: "Re: Choosing a Windows Database"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 5 Jan 2005 10:36:06 +1000
It'll be the "Express" edition of SQL Server. Installer target size though
is around 36M last I heard. But well worth considering. Rather than being
installed as a separate instance for each application on the system, people
will install it once and each app will then only basically have the db file
to be copied/installed along with your app.
HTH,
-- Greg Low [MVP] MSDE Manager SQL Tools www.whitebearconsulting.com "Ralph" <msnews.20.nt_consulting32@spamgourmet.com> wrote in message news:e5ZMMJr8EHA.3336@TK2MSFTNGP11.phx.gbl... > > "Mitchell Vincent" <mitchell.vincent@gmail.com> wrote in message > news:OFZjpTp8EHA.2196@TK2MSFTNGP11.phx.gbl... >> It's a hard decision these days! >> >> I write a lot of shareware, mostly business apps and they almost always > use >> some kind of relational database. Until now I've been using SQLite, but > with >> my recent move to .NET, the SQLite ADO.NET provider is in an unusable >> beta >> state so I've got to move on. I'm looking for something affordable > ($500ish >> or below), something SQL aware, something that multiple users can access > and >> something scalable and fast. Here is what I've found so far, and why I > like >> or don't like it : >> >> SQLite - Impressive little library but developed for *ix and > cross-compiled >> using MinGW, that makes me nervous. It also has no decent ADO.NET or ODBC >> provider. >> >> Access - Probably the most obvious choice, but I've heard so many >> conflicting reports of how great it is and how crappy it is that I have >> no >> choice but to believe no one and stick Access in as a last resort. I just >> don't know if it's scalable enough for multiple user concurrent access. >> >> Firebird (firebird.sourceforge.net) - Impressive because it's free, but > the >> embedded version only allows for single user access to the database file, >> that knocks it out of the running for most of my apps. It is based on the >> Interbase code released back in 2000. >> >> MS-SQL/Orcale/<Insert your big name RDBMS here> - Just too expensive. >> >> MSDE - If it weren't 70 megs to distribute, maybe. That is WAY over what >> I >> would want users to have to download for a trial or something >> >> CodeBase (www.codebase.com) - Really fast little embedded system. The > "SQL" >> version is nothing more than an ODBC driver for the DBF/xBase files. >> Don't >> know how much I'd trust that in a multi-user environment. Please, take me > to >> school if I'm wrong for being afraid of using ODBC through .NET. >> >> TurboDB (www.turbodb.com) - Much like CodeBase (I think?) but with native >> ADO.NET provider(s). Not sure how well I'll be able to use something like >> this as I've always used "real" RDBMSs like PostgreSQL and such. >> >> That's about it. I'd be willing to guess that there are a million others > out >> there using the DBF type files. Ideally the database I'd like would > support >> multiple concurrent users, SQL, a rich set of data types and have an > ADO.NET >> provider (or anything that supports that IList interface, according to >> the >> developer of a control we use). >> >> Many thanks! >> >> -- >> - Mitchell >> > > You can also add MySQL to the list: > http://dev.mysql.com/downloads/mysql/4.0.html > Unfortunately it isn't that small either (20+mb). > > You might consider providing the database as a separate install and let > the > client chose their backend. You could offer MySQL, MSAccess, and MSDE. > (Incidently, the latter is going thru another re-interation - not sure > what > the new name is going to be.) > > -ralph > > > >
- Next message: BWOlson: "Re: Visual Basic 6.0 and Access 2000"
- Previous message: Ralph: "Re: Choosing a Windows Database"
- In reply to: Ralph: "Re: Choosing a Windows Database"
- Next in thread: Mitchell Vincent: "Re: Choosing a Windows Database"
- Reply: Mitchell Vincent: "Re: Choosing a Windows Database"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
