Carlos,

One other thing. If you are pumping the data in a
Destination: Insert
Source: Delete
Then using a joint DB transaction is pretty important to guarantee no
missing data or double entries.
If just:
Destination: Insert
Then I would use a TX for each DB as it will reduce the possibility of Limbo
Transactions if either server crashes. Finally, if you use 2 tx's you can
also make the application multi-threaded and may get perf benefits from
having 1 worker thread reading the data and multiple worker threads
inserting the data (each thread needs its own connection).

Cheers,

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

""Ann W. Harrison"" <aharrison@...> wrote in message
news:5.1.0.14.2.20021014145108.02a4ed90@......

> At 03:33 PM 10/14/2002 -0300, Carlos H. Cantu wrote:
> >Hello !
> >
> >Does anybody had played with this :
> >
> >When doing a Pump between 2 databases, what is the best option
> >regarding performance : Keep both of them sharing the same transaction
> >or keep separated transactions for each one ?
>
> In theory, it should make no difference. If you have a common
> transaction, all it does is coordinate operations between child
> transactions, one in each participating database. So there's
> slightly less overhead if you open a transaction in each database.
>
>
>
> Regards,
>
> Ann
> www.ibphoenix.com
> We have answers.
>
>
>
>
> 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/
>
>
>