Re: Suggestoins for Local DB to use with Shareware

In article <4454a01e$1@xxxxxxxxxxxxxxxxxxxxxx>, nospam@xxxxxxxxx says...
Hi!

G. Bradley MacDonald wrote:
Hello Everyone,

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

DBISAM (www.elevatesoft.com). I use it in very small applications / tools up
to multi user systems. It simply works and does not hinder you to do the
job.

...
It should have the following:

The DB should fully support SQL.

Yup.

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

No.
OK - I could live with that. I do now with Advantage.

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.

Char up to 512 and memo fields.
Yes - I was reading about it on their site. This would do.


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.

Sorry, but it is very hard to build a Delphi application with such a small
footprint. But with a really good EXE packer, it's possible. The footprint
of DBISAM is really small, but because my applications are up to 20 mb, I
don't know if the footprint is 200k or 400k.
Sorry - I meant the add on for the DB - not my app. It is already in
the 10MB range. I just didn't want to have to have a 20+MB download for
the DB.


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.

All integrated db systems I know use their own tabkle components. In DBISAM,
it's TDBISAMTable (and TDBISAMQuery). I don't think that there is anything
working with Borlands TTable components.
That is a problem right there. It is becoming more and more important
for me not to have to use special components - as I want to use the same
code on the local DB as the larger DB - such as MS SQL, etc.

The issue of having a default size of 4GB may be an issue. Even the
local database could grow quite large. For some customers - it would be
saving 200,000+ "records" each time - and each of those records can be
3KB in size. I note that is says you can go up to 128GB which should be
fine - but it is a concern that is it not supported as the default.
Makes me wonder why.


thanks for your comments!


Ralf

--

G. Bradley MacDonald
bradley_AT_telus_DOT_net
.

Relevant Pages

  • Re: Stray poll: DBs for Delphi non-tech
    ... I use DBISAM for Win32 applications. ... and with the regular Win32 client for accessing the web database from Win32 ...
    (borland.public.delphi.non-technical)
  • Re: Stray poll: DBs for Delphi non-tech
    ... > databases were most people here primarily using and deploying to? ... > (list only the top two or three DBs for your applications) ... Dbisam and SQL Server. ...
    (borland.public.delphi.non-technical)
  • Re: Strange DBISAM error
    ... > TemporaryPath ... all DBISAM queries in all applications ... DBISAM system utility do not work as well. ... It seams that only .DAT file cannot be created, ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: Any grid controls that can handle this?
    ... I will be using DBISAM which does support SQL and can easily write a ... Just wondering what 3rd party grid will allow me to implement this most ... Prev by Date: ...
    (borland.public.delphi.thirdpartytools.general)