Hi guys, I'm back with my next question!

OK, say I have 2 remote servers (well one is just set up to use localhost
but never mind that), I want to do something along the lines of:

SELECT * INTO RemoteMachine1::Table1
FROM  RemoteMachine2::Table2
WHERE <WholeBunchOfStuff>

What is the best/correct way of doing this?

My ideas are:

1. Have 2 Sessions, each pointing at each remote machine. And do

Session1: SELECT * INTO memory\tmp FROM table1
Session2: SELECT * INTO Table2 FROM memory\tmp

Which leads me onto the Q - what is the scope of memory tables? Session or
Application?

or

2. Have 1 Session and do

Point Session at Machine1
SELECT * INTO memory\tmp FROM table1

Point Session at Machine2
SELECT * INTO table2 FROM memory\tmp

or

3. Other??

Thanks you guys,

Regards,

Tim.

Tim,

<< What is the best/correct way of doing this? >>

How many records are involved ?  If it isn't a ton, then using the
SaveToStream/LoadFromStream methods will work fine:

http://www.elevatesoft.com/dbisam4d5_loading_saving_streams.htm

Just be sure to empty the target table before loading the stream if you want
the data completely replaced.

<< Which leads me onto the Q - what is the scope of memory tables? Session
or Application? >>

Application.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hello Tim Young [Elevate Software],

> Tim,
>
> << What is the best/correct way of doing this? >>
>
> How many records are involved ?  If it isn't a ton, then using the
> SaveToStream/LoadFromStream methods will work fine:


It will normally be quite a lot > 50,000 records at a time...... is this
too much for your suggestion?



>
> http://www.elevatesoft.com/dbisam4d5_loading_saving_streams.htm
>
> Just be sure to empty the target table before loading the stream if
> you want the data completely replaced.
>
> << Which leads me onto the Q - what is the scope of memory tables?
> Session or Application? >>
>
> Application.
>

Tim,

<< It will normally be quite a lot > 50,000 records at a time...... is this
too much for your suggestion? >>

It could possibly be - what is the record size of the table ?  If it is over
400-500 bytes, then you are probably going to want to use another method.

--
Tim Young
Elevate Software
www.elevatesoft.com