I would use a delta database, i.e. a database with the same structure
without indices, triggers and procedures. Then use replication (we use our
own), to populate the delta database, then zip this up, put it on CD, unzip
it at the other end and replicate into the main database.

If this sounds like a plan, you will need to add some tables and triggers to
work out which rows have changed. How frequently do you do the update, how
large is the whole DB and what % of it changes (by size) from one update to
the next?

I've done this before, + or - complexity for lots of clients. We have even
run overnight replication over telephone lines before now, it is surprising
how much data you can synchronize overnight.

JAC.
Jason Chapman
JAC2 Consultancy

Training - Development - Consultancy
Delphi, InterBase, Firebird, OOAD, Development lifecycle assistance,
Troubleshooting projects, QA.....
www: When I get round to it....
Mob: (+44) 07966 211 959 (preferred)
Tel: (+44) 01928 751088

"Milan Babuskov" <milanb@...> wrote in message
news:3E07325D.7080408@......

> benno wrote:
> > Just a suggestion, but why don't you simply backup and restore, using a

CD

> > as a carrier? You could even automate it using a bat file and gbak I

guess.

>
> I don't need the whole database, just the difference since last data
> transfer.
>
> I also need to add the data to main database, but only to add. The main
> database is filled with new data on main site, so I cannot just restore
> over it.
>
> Milan.
>
>
>
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>