Re: OPENROWSET doesn't work, OPENDATASOURCE does (bug?)
- From: Sue Hoegemeier <Sue_H@xxxxxxxxxxxxx>
- Date: Tue, 26 Jul 2005 20:47:39 -0600
It can work against another server but if you feel you have
hit a bug, you can open a case with Product Support. If it
is a bug, you won't be charged.
-Sue
On Tue, 26 Jul 2005 10:28:49 -0500, "Mike Kiefer"
<mdk-online@xxxxxxxxxxxxxx> wrote:
>Oddly enough, the error goes away, but the select is executed on the local
>copy of the Northwind database instead of the remote copy such that I get
>the incorrect rows. That's almost worse than getting an error. It certainly
>looks like there is some sort of bug here.
>
>Mike
>
>"Sue Hoegemeier" <Sue_H@xxxxxxxxxxxxx> wrote in message
>news:3e9ce15f3o8sotbsg2n033vpt41qbg5qhi@xxxxxxxxxx
>> Try something like:
>> select *
>> from OpenRowset('SQLOLEDB',
>> 'Trusted_Connection=Yes;Database=Northwind;Integrated
>> Security=SSPI;Data Source =YourServer','select * from
>> Shippers')
>>
>> -Sue
>>
>> On Mon, 25 Jul 2005 22:48:32 -0500, "Mike Kiefer"
>> <mdk-online@xxxxxxxxxxxxxx> wrote:
>>
>>>I'm having trouble troubleshooting a remote query using OPENROWSET. For
>>>some
>>>reason I can get OPENDATASOURCE to work with a given connection string but
>>>using OPENROWSET with the same connection string fails. I'm a bit baffled.
>>>It seems like it should work basically the same way using either method,
>>>as
>>>shown below. (I am running these queries as sa/dbo.)
>>>
>>>Any help in troubleshooting would be appreciated.
>>>
>>>-- THIS WORKS
>>>SELECT *
>>>FROM OPENDATASOURCE(
>>> 'SQLOLEDB',
>>> 'Data Source=MYSERVER;Integrated
>>>Security=SSPI').Northwind.dbo.Shippers
>>>
>>>-- THE NEXT STATEMENT FAILS WITH THE FOLLOWING ERROR(S):
>>>-- Server: Msg 7399, Level 16, State 1, Line 1
>>>-- OLE DB provider 'SQLOLEDB' reported an error.
>>>-- [OLE/DB provider returned message: Invalid authorization specification]
>>>-- [OLE/DB provider returned message: Invalid connection string attribute]
>>>-- OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
>>>IDBInitialize::Initialize
>>>returned 0x80004005: ].
>>>
>>>SELECT *
>>>FROM OPENROWSET(
>>> 'SQLOLEDB',
>>> 'Data Source=MYSERVER;Integrated Security=SSPI', 'SELECT * FROM
>>>Northwind.dbo.shippers')
>>>
>>>
>>>Thanks in advance,
>>>Mike
>>>
>>
>
.
- References:
- OPENROWSET doesn't work, OPENDATASOURCE does
- From: Mike Kiefer
- Re: OPENROWSET doesn't work, OPENDATASOURCE does
- From: Sue Hoegemeier
- Re: OPENROWSET doesn't work, OPENDATASOURCE does (bug?)
- From: Mike Kiefer
- OPENROWSET doesn't work, OPENDATASOURCE does
- Prev by Date: Re: SQL Server Enterprise Manager
- Next by Date: Few Question regarding C#
- Previous by thread: Re: OPENROWSET doesn't work, OPENDATASOURCE does (bug?)
- Next by thread: MTU setting for SQL 2000 + VPN
- Index(es):
Relevant Pages
|
