Re: Thanks, but..
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Tue, 14 Jun 2005 22:07:38 +0000 (UTC)
Zorpiedoman (nowheremane@xxxxxxxxxxx) writes:
> Thanks Erland, however the error message leads me to believe that may
> not be the cause. The error is saying:
>
> Invalid Object Name 'BS2.BS2.dbo.Accounts'
Moral: always include the error message you are getting.
I used the SQL Profiler to see what Enterprise Manager is up to. It turns
out that it generates this command:
exec sp_executesql N'UPDATE "JUNI.bos_sommar"."dbo"."currencies" SET
"curpriceib"=@P1 WHERE "curcode"=@P2 AND "curname"=@P3 AND ...
Note how the first pair of " are placed. That does not mean the linked
server JUNI and the database bos_sommar. That means the database
"JUNI.bos_sommar".
Thus, a pure and plain bug.
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
.
- Follow-Ups:
- Re: Thanks, but..
- From: Zorpiedoman
- Re: Thanks, but..
- References:
- Linked Server and Views
- From: Zorpiedoman
- HOWEVER...
- From: Zorpiedoman
- Re: HOWEVER...
- From: Erland Sommarskog
- Thanks, but..
- From: Zorpiedoman
- Linked Server and Views
- Prev by Date: Re: Syntax error (missing operator) when deleting a row with comma
- Next by Date: Access Oracle 10g using Oracle OLE DB provider
- Previous by thread: Thanks, but..
- Next by thread: Re: Thanks, but..
- Index(es):
Relevant Pages
|
|