I have an elevatedb database with more than 10 tables. I put the database under a dropbox folder. It is synced to other computers when I make a change to a table. The sync is fast becuase the size of a table file is small. If elevateDB change to a single file system, a small change to a single table will cause the whole database to be synced. It will slow down the sync significantly and even make this not practicle. I hope Tim will not move to a single file database in elevateDB version 3.

Xiannong


That post somewhat baffles me. Why should syncing a table in a single file database system take any longer than in a windows file based approach. It may well be even faster since Tim will be in (almost) total control of how and when data is read/written.

It may be that you're confusing what a single file database system is all about. Currently a table is up to three Windows files. Unless Tim does something very strange I think there will be the analogues of those files in the single file database. I could see the index file splitting into a one file per index (bit like Paradox) and the blob file being merged into the other data via variable length records but that's about the extent of my imagination. Or at least the sane part of it, I do know of and have used (way in the past) some really freaky data structures.

I'll be fascinated to see what Tim does do eventually.

Roy Lambert [Team Elevate]

Xiannong

Please take care using a product like DropBox to sync your DB across different network computers! I use DropBox & it is amazing for things like Word documents. However Elevate has a powerful engine / server which can be run on a network accessible PC or over the net via IP Address. This allows distant users to all access the database, but ensures all updates etc., obey the logic of the Database.

If you want to sync different networks without a central server holding the shared files you can write SAVE UPDATE / LOAD UPDATE and COPY FILE procedures on the server ... again this is "data safe", whereas DropBox is not! 2 users changing the same table at the same time via a shared DropBox would over-write each others changes ... which could be very bad.

Adam

Adam


Woops. My brain didn't sync on DropBox

Now I've caught up with that I would also recommend checking out PUBLISH - this should be even faster than small tables since its just going to be writing changes out. Might be a bit difficult to get it working with DropBox though.


Roy Lambert

Xiannong,

<< I have an elevatedb database with more than 10 tables. I put the database
under a dropbox folder. It is synced to other computers when I make a change
to a table. The sync is fast becuase the size of a table file is small. If
elevateDB change to a single file system, a small change to a single table
will cause the whole database to be synced. It will slow down the sync
significantly and even make this not practicle. I hope Tim will not move to
a single file database in elevateDB version 3. >>

As Adam and Roy pointed out, you should consider using the built-in
replication for ElevateDB in order to do what you're attempting:

http://www.elevatesoft.com/manual?action=viewtopic&id=edb2sql&topic=Replication

You can still use a dropbox folder, but instead of directly copying the
table files, you'll simply perform a SAVE UPDATES operation and then copy
the update file (.edbupd) up to the dropbox folder.  On the other ends,
you'll have any other locations just use a LOAD UPDATES operation to load
the updates.  This will give you even better performance and be completely
perfectly safe in terms of locking, etc.

--
Tim Young
Elevate Software
www.elevatesoft.com