Re: errors calling linked oleDB server stored procedures
From: gerry (germ_at_hotmail.com)
Date: 04/28/04
- Next message: Dinesh T.K: "Re: Returning the Server Name"
- Previous message: Chris Savedge: "Re: Update Query"
- In reply to: Michael, Cheng [MSFT]: "Re: errors calling linked oleDB server stored procedures"
- Next in thread: Michael, Cheng [MSFT]: "Re: errors calling linked oleDB server stored procedures"
- Reply: Michael, Cheng [MSFT]: "Re: errors calling linked oleDB server stored procedures"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 28 Apr 2004 12:18:43 -0400
Thanks again for the reply.
The remote database is not DB2 , it is uniVerse.
Remote procedure calls work fine via adoDB using the same oleDB provider
both with & without parameters but neither work with SQL server's
OpenQuery()
I think you are right, although the documentation states that this should
work , SQL server appears to have a BIG hole in its support for non-sql
server linked servers. Every other oleDB aware language/system/package i
have tried has no problem with invoking remote stored procedures using this
provider and successfully using the returned dataset.
thanks for you time with this issue.
""Michael, Cheng [MSFT]"" <v-mingqc@online.microsoft.com> wrote in message
news:CLPdCyRLEHA.308@cpmsftngxa10.phx.gbl...
> Hi Gerry,
>
> Thanks for you instant reply.
>
> First of all, I have no idea about IBM.uniOLEDB, it is not supported by
> Microsoft. So I am not sure whether the provider you used could support
> remote call DB2 stored procedure and the error message is thrown by
> IBM.uniOLEDB. Would you have a check that it support reomte stored
> procedure call?
>
> Secondly, would you please try to call a stored procedure without dynamic
> parameter, like OPENQUERY (LinkedTableName, "call TestProc"), will it give
> you right answer? I am not sure the correct syntax of DB2.
>
> Thirdly, I think you could try using four-part named stored procedure
> instead of OPENQUERY like
> LinkedTableName.databaseName.ownerName.storedProcedureName
>
> Anyway, I am convinced that running stored procedures from DB2 Server is
> not supported by SQL Server, even you may get result, it is not reliable.
>
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know.
>
> Sincerely yours,
>
> Michael Cheng
> Microsoft Online Support
> ***********************************************************
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks.
>
- Next message: Dinesh T.K: "Re: Returning the Server Name"
- Previous message: Chris Savedge: "Re: Update Query"
- In reply to: Michael, Cheng [MSFT]: "Re: errors calling linked oleDB server stored procedures"
- Next in thread: Michael, Cheng [MSFT]: "Re: errors calling linked oleDB server stored procedures"
- Reply: Michael, Cheng [MSFT]: "Re: errors calling linked oleDB server stored procedures"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|