|
Home > Archive > IQ Server > March 2006 > Remote login for "Insert Location"
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Remote login for "Insert Location"
|
|
| Sherlock, Kevin 2006-03-21, 8:33 pm |
| I have a remote server (TOKYO) of class asejdbc. I have setup a remote login
for DBA to this server to login as "sa" and it's appropriate password
When I send a "FORWARD" statement from IQ while logged in as DBA, it connects as
"sa" and issues the statement. Exactly what I would expect.
However, when I load a table using "INSERT <tablname> LOCATION 'TOKYO.mydb' {
select * from mytable }", the connection to TOKYO is attempted as "DBA" ( the
table owner), and not my remote login.
This seems to me like an undocumented feature. Can anyone tell me how to force
INSERT LOCATION to use the remote login to ASE?
| |
|
| from what i understand to use the 'insert location' syntax
you must
setup the exact same ID and PASSWORD on both servers and log
into IQ with the ID...i read that somewhere in the
documentation...that is the only way i got it to work. I
have 8 ID's that i created in IQ and ASE to run 8 load
streams using insert location
> I have a remote server (TOKYO) of class asejdbc. I have
> setup a remote login for DBA to this server to login as
> "sa" and it's appropriate password
>
> When I send a "FORWARD" statement from IQ while logged in
> as DBA, it connects as "sa" and issues the statement.
> Exactly what I would expect.
>
> However, when I load a table using "INSERT <tablname>
> LOCATION 'TOKYO.mydb' { select * from mytable }", the
> connection to TOKYO is attempted as "DBA" ( the table
> owner), and not my remote login.
>
> This seems to me like an undocumented feature. Can anyone
> tell me how to force INSERT LOCATION to use the remote
> login to ASE?
>
>
| |
| Sherlock, Kevin 2006-03-22, 1:33 pm |
| Thanks John, and never mind anyway. There apparently is a CR for this behaviour
(which by the way is expected to use a remote login for INSERT LOCATION if you
have one setup). CR is targeted for "late 2Q 2006". Grrr...
CR #303044
Description - INSERT...LOCATION with different logon user
Fixed in - 12.6.1 which is currently targeted in late Q2 06
Note from CR -
insert location will now attempt to connect to the remote server using an
externlogin if one has been created. If an externlogin has not been created,
then the connection attempt will be made using the currently connected userid
and password.
<John> wrote in message news:4420858e.65b8.1681692777@sybase.com...[color=darkred]
> from what i understand to use the 'insert location' syntax
> you must
> setup the exact same ID and PASSWORD on both servers and log
> into IQ with the ID...i read that somewhere in the
> documentation...that is the only way i got it to work. I
> have 8 ID's that i created in IQ and ASE to run 8 load
> streams using insert location
>
|
|
|
|
|