Re: Suggestoins for Local DB to use with Shareware



"G. Bradley MacDonald" wrote

I am looking for suggestions for a good local DB for our shareware app.

The DB should fully support SQL.

It would be nice if it only had one actual file - storing all the
tables/indexes, etc in that one file.

I would choose MS Access...

It must be able to handle string fields of up to 512 characters in size.
Larger would be nice. It would even be better if it they were like
VarChar fields in a relational database and only took up the size that
was used.

Yep,it has a fixed length text field (same as VarWChar) limit of 255 char
and a memo field (same as LongVarWChar) limit of 1.2MB (IIRC) and a Blob
field for binary data.

The MS Access fields correspond nicely with MS SQL fields and I once wrote a
..NET v1.1 app that used the ubiquious NorthWind database in either MS Access
or MS SQL and you could switch between database engines by merely changing
the connection string. Also the MS SQL data migration tools make simple work
of upgrading data from MS Access to MS SQL. I use the Office version of
Access to build and maintain the Access databases, any version works just
fine for that purpose.

It must have a low foot print in terms of size. This is shareware and
is downloadable. Somewhere arount 1 to 2 MB would be tollerable.

How about zero (0) foot print!

We will also be supporting MS SQL, Oracle, Interbase - for larger
customers - but want to support a local DB for smaller customers. So -
this DB must be able to support SQL as its main way of accessing the
data. It MUST be accessable using Borlands standard components - no
special TTable derivities is important.

The SQL used in MS Access meets your requirements. It also supports Views
and Procedures. Other features available from Delphi W32 is the ability to
compact and/or repair the database. And you can have a simple password that
keeps nosey folks with Access for being able to get into the database.

IMO the MS Access database is ideal for your requirements. And it's Jet-4
provider will be available on Vista if that means anything to you...


.



Relevant Pages

  • Re: CREATE AGGREGATE failed because type Concatenate does not conform to UDAGG specification due to
    ... Go to the Database tab and click on the browse button next to the connection string. ... In the New Database Reference dialog, enter the details for the database where you want to deploy the assembly and create the user defined aggregate. ... I'm trying to do some CLR integration with sql server 2005. ...
    (microsoft.public.sqlserver.programming)
  • CREATE AGGREGATE failed because type Concatenate does not conform to UDAGG specification due to meth
    ... Now register the assembly and the aggregate in the SQL Server database you want ... I'm trying to do some CLR integration with sql server 2005. ...
    (microsoft.public.sqlserver.programming)
  • Re: dbdebunk Quote of Week comment
    ... > a lot of really bad SQL programmers. ... But SQL does not have a pointer data type or the ... > being told to design a database. ... But why is little Cindy Lou Who employee ...
    (comp.databases.theory)
  • Re: DBMS and lisp, etc.
    ... Naively implemented with SQL, again for 10 ... (1 query for the initial orders, 1 query for each order for its ... soon as you upgrade to the SQL database. ... (eq (order-customer orderA) ...
    (comp.lang.lisp)
  • Re: dbdebunk Quote of Week comment
    ... > a lot of really bad SQL programmers. ... a surrogate key should support the primary key. ... But SQL does not have a pointer data type or the ... > being told to design a database. ...
    (comp.databases.theory)