linked server

Anyone know a quick was to create a linked server to a view on another server
without drudging thru the books on line description? Thanks everyone for
being
there, you have all been very helpful
Hi,
See the below article.
http://www.microsoft.com/India/msdn/articles/166.aspx
Thanks
Hari
SQL Server MVP
"coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
news:EA09DBBC-7C2E-4FB2-B030-F0B687918805@.microsoft.com...
> Anyone know a quick was to create a linked server to a view on another
> server
> without drudging thru the books on line description? Thanks everyone for
> being
> there, you have all been very helpful
|||the easiest way is to go into EM, Open Security\Linked server
Right click and add new.
After entering the name, and clicking SQL server
go into security and click Be made using this security acct and enter the
info you should be good to go.
When calling tables or view you need to qualify the tables with
server.DB.DBO.TbaleName
HTH,
Joe
|||"jaylou" wrote:

> the easiest way is to go into EM, Open Security\Linked server
> Right click and add new.
> After entering the name, and clicking SQL server
> go into security and click Be made using this security acct and enter the
> info you should be good to go.
> When calling tables or view you need to qualify the tables with
> server.DB.DBO.TbaleName
> HTH,
> Joe
|||Thanks Hari, that was very helpful,
I'm able to launch a view to a linked server, but when I attempt to
save the view, I receive the following error message in part:
ODBC error:[ Microsoft][ODBC SQL Server Driver][SQL Server] The operation
could not be performed because the OLE DB provider ‘SQLOLEDB’ was unable
to begin a distributed transaction …. OLE/DB provider returned
message :
New transaction cannot enlist in the specified transaction coordinator…
If experienced a similar problem when linking and saving views to
an oracle db. The solution was to install various oracle patches. Could
this be a similar problem or something else?
"Hari Prasad" wrote:

> Hi,
> See the below article.
> http://www.microsoft.com/India/msdn/articles/166.aspx
> Thanks
> Hari
> SQL Server MVP
> "coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
> news:EA09DBBC-7C2E-4FB2-B030-F0B687918805@.microsoft.com...
>
>
|||Hi coenzyme,
I had the same error message few days ago when I tried to INSERT into local
table but joining it with a remote view in the same statement.
I think this error occurs when you try to do an UPDATE/INSERT and have
remote view specified in the statement on which you don't have write
permission.
I only had read access to remote view but had db_owner access to local
database.
I couldn't test a solution because I was not able to modify the remote view.
The workaround I found to this problem is to create a temporary table in
local database, get all related rows transferred to local table and join this
table in UPDATE/INSERT statement.
Let me know if you find another solution.
Regards,
Fahim Ahmed
"coenzyme" wrote:
[vbcol=seagreen]
> Thanks Hari, that was very helpful,
> I'm able to launch a view to a linked server, but when I attempt to
> save the view, I receive the following error message in part:
> ODBC error:[ Microsoft][ODBC SQL Server Driver][SQL Server] The operation
> could not be performed because the OLE DB provider ‘SQLOLEDB’ was unable
> to begin a distributed transaction …. OLE/DB provider returned
> message :
> New transaction cannot enlist in the specified transaction coordinator…
> If experienced a similar problem when linking and saving views to
> an oracle db. The solution was to install various oracle patches. Could
> this be a similar problem or something else?
>
> "Hari Prasad" wrote: