Item two: Injecting an intermediary.

If you wanted to copy data from one SQL server database to another would
you really run the transfer from an intermediate client? Or would you run
it from either the sending or the receiving server? I would always run it
from a server and bypass the intermediate client for a number of reasons.
One being servers are often on a faster backbone, especially when in the
same room. For example 10GB versus 1GB. And sometimes even virtualized!
Two, even if the servers are not in the same room do you really want to
send from your CHINA server to your RUSSIA server by way of your OMAHA pc?
"...by way of Omaha" comes to mind. "Uneasy rider".

But let's say I do have this Mimix server, with these relational database
entries:
Remote
Entry Location
GDISYS *LOCAL
GDISYS1 GDISYS1
GDISYS2 GDISYS2

Relational database . . . . . . : GDISYS
Relational database alias . . : GDISYS1
Remote location:
Remote location . . . . . . . : GDISYS1
Type . . . . . . . . . . . . : *IP
Port number or service name . : *DRDA

And this other Mimix server, with these relational database entries:
Remote
Entry Location
GDISYS *LOCAL
GDISYS1 gdisys1
GDISYS2 GDISYS2
Relational database . . . . . . : GDISYS
Relational database alias . . : GDISYS2
Remote location:
Remote location . . . . . . . : GDISYS2
Type . . . . . . . . . . . . : *IP

and I just had the time and network to piss away then I might do this from
Run SQL Scripts.
First, I tell it to connect to GDISYS1.
Then I would run the following:
create table rob.rcox2 as (
select * from gdisys2.erplxf.rco)
with data;
create table rob.rcox2 as ( select * from gdisys2.erplxf.rco) with data
Statement ran successfully (450 ms)
Then I would verify it with
select * from rob.rcox2

and I see all the data.

Both lpars are at 7.2.




Rob Berendt

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].