Re: Easily distributable database

On Mon, 23 Jul 2007 13:10:08 -0700, JB <jamesb457@xxxxxxxxx> wrote:

I'm writing a data driven app, its all just about finished but i
havent decided how to store the data.

I'm looking at some form of database. Requirements:
Easy to Distribute, hopefully just some hard disk files.
Relatively quick to query.
I think in this case, speed is secondary to ease of use for the end
user. Although speed is always important, which is why i wont be using
xml :)

Data *shouldnt* get any bigger than 1GB (it shouldnt get more than a
few hundred meg but i'd like room for expansion).

My choices:
1) Access: Easy to use, distributes as stand alone files.
But then i'd have to go out and buy a copy of office :(
2) SQLite, never used it, oonly just heard of it today, starting to
read up about it now, seems like it will work similarly to access
(from the outside at least), dont know how the speed is though.
3) SQL Server Express: "Free to download, free to redistribute, free
to embed" according to microsoft.
It seems like a really good option, a free SQLServer seems like it
would be incredibly flexible and fast. But I am concerned about how
easy it would be to distribute with a prog? Will any potential users
have to download the sql server express app? or a couple of run-time
files? or nothing?
4) Fill in the blanks. Any other suggestions?

Opinions welcomed and appreciated.

Hi

SQL Server would be the best choice IMHO. It sounds perfect for your
requirments and with the advanced version (also free) you can have
full text searching and other SQL Sqerver features. Databases can be
up to 4gb in size.

It can be deployed using ClickOnce technology so you should have no
problems distributing it with your app. You might want to read this

http://msdn2.microsoft.com/en-us/library/Bb264562.aspx

HTH

Cheers
Steve

.

Relevant Pages

  • Re: Webservices - the way to go...?
    ... about your lack of secure network connectivity your between a rock and a ... To summarize the posts so far: you have a winform app. ... using a webservices data layer to handle all the database interactions. ... Upgrade your database to SQL Server. ...
    (microsoft.public.dotnet.general)
  • Re: MSVC++ app type choice, form design questions
    ... > 1) MSVC Project definition requires that for an MFC app I choose ... MFC's built-in database support is really built around the document/ ... with the full version of SQL Server, but it's still pretty usable -- ...
    (microsoft.public.vc.mfc)
  • Re: SQL Licensing
    ... it depends on the features you used in your database development. ... If your app works with Express, then go with it not to buy license for SQL Server instances. ...
    (microsoft.public.sqlserver.clients)
  • Re: MSDE users guide
    ... You are "right on" with your understanding of my problem. ... I am going to download the ... MSDE is missing a key component of SQL Server, ... basic tool for database creation and probing existing databases. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: MSVC++ app type choice, form design questions
    ... >> 1) MSVC Project definition requires that for an MFC app I choose ... At startup the end user sees a summary of the database contents. ... MDAC has full built-in support ... >competing with the full version of SQL Server, ...
    (microsoft.public.vc.mfc)