Linked server from SQL2012 to SQL2000

I need to set up a linked server to a SQL 2000 server from my new SQL 2012 server. I see that the Native Client does not support access to SQL 2000. What is a supported method/client I can use?

Hello,
Please see the workarounds in the following link:
"It works through MSDASQL provider and an ODBC Data Source (datasource also configured with SQLNCLI10) :
EXEC master.dbo.sp_addlinkedserver
@server = N'TEST1' , @srvproduct = N'SQLSERVER' , @provider = N'SQLNCLI10' , @datasrc = N'MyServer\SQL2000';
-- works only with distributed transactions even for SELECT
EXEC master.dbo.sp_addlinkedserver
@server = N'TEST2', @srvproduct=N'MSDASQL', @provider = N'MSDASQL', @datasrc=N'SQL2000DataSource', @location=N'System';
-- works as it should be "
http://connect.microsoft.com/SQLServer/feedback/details/731869/using-sqlncli10-to-create-a-linked-server-to-sql-server-2000-causes-a-fault#details
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Similar Messages

Linked Server from SQL 2008 to Connect to 2012 read only replica never works

I have two Production Database Servers
1. SQLServer2008 (2 Nodes Cluster)
2. SQLServer2012 with 2 read only replica (3 Nodes Cluster)
I would like to draw a line here, We have routing table and URL working perfectly fine.
We have tested LINKED Server from 2012 Box to production Server by Specifying APPLICATIONINTENT = ReadOnly; it works perfectly fine, the routing is being used.
When we create linked server from SQL Server 2008 Box (Please note we have installed SQL Server 2012 Client tools on this box and Restarted the Servers) using the below script
USE [master]
EXEC master.dbo.sp_dropserver @server=N'AGL1', @droplogins='droplogins'
GO
EXEC master.dbo.sp_addlinkedserver @server = N'AGL1'
,@datasrc='AGL1'
,@provider='SQLNCLI11'
,@provstr='ApplicationIntent=ReadOnly;Database=AdventureWorks2012'
Linked Server is created, Now when I run the Query
exec ('select @@servername') at AGL1
It always brings the Primary READ/WRITE node name only, after lots of research I found that, this linked Server is always using SQL Native Client 10.0 only, even after creating Linked Server using SNC 11, That is the reason it is not going to routing
table. Its always connecting to Primary node.
Below is the way I found it, on 2012 Production Server I executed below Query
SELECT session_id, protocol_type, driver_version =
CASE SUBSTRING(CAST(protocol_version AS BINARY(4)), 1,1)
WHEN 0x70 THEN 'SQL Server 7.0'
WHEN 0x71 THEN 'SQL Server 2000'
WHEN 0x72 THEN 'SQL Server 2005'
WHEN 0x73 THEN 'SQL Server 2008'
ELSE 'SQL Server 2012'
END,client_net_address ,client_tcp_port,local_tcp_port ,T.text
FROM sys.dm_exec_connections
CROSS APPLY sys.dm_exec_sql_text(most_recent_sql_handle) AS T
The help is taken from msdn (Link Provided below) for the above Query
https://msdn.microsoft.com/en-us/library/dd339982.aspx
and I found it always uses SQL Server 2008 SNC.
My Question is, is there a way to force SQL Server to use SQL Server Native Client 11.
Has anyone tried this setup?
Thank you in advance.

Unfortunately no, there is no other way of forcing it without restart. The SQL Server stack has no idea of the existing Native Client as it booted prior its installation. And you cannot force "DLL reload" without proper service restart.
Ivan Donev MCT and MCSE Data Platform

Have trouble query after creating a linked server from SQL Server 2008 to EXCEL 2007

I created a linked server from SQL Server 2008 Management Studio Express to an EXCEL 2007 workbook using:
sp_addlinkedserver @server='LSERVER_EX0', @srvproduct='EXCELDATA', @provider='Microsoft.ACE.OLEDB.12.0', @datasrc='C:\Temp\abc.xlsx', @provstr='EXCEL 12.0'
The linked server LSERVER_EX0 was created, but I cannot see any table(excel sheet), and when i ran the following to query tables,
sp_tables_ex 'LSERVER_EX0'
I got:Cannot obtain the schema rowset "DBSCHEMA_TABLES" for OLE DB provider "Microsoft.ACE.OLEDB.12.0" for linked server "LSERVER_EX0". The provider supports the interface, but returns a failure code when it is used.
Any hint why?
on another note, i was able to import the EXCEL sheets using the Import and Export Data wizard, but i cannot control the column data type and size in this way.

Open management studio, goto "Server Objects"->"Linked Servers"->Providers, select the provider you use, right click it and in provider options, check "Allow inprocess".

Syntax to query a MSSQL 2008R2 linked server from Oracle

Hi,
    I would know if it's possible to query a MSSQL 2008R2 linked server from Oracle. Actually I can query local MSSQL databases from Oracle using dg4odbc without problem but how can I query the linked servers configured on the MSSQL side ?
From MSSQL, I can query those linked servers using the [linked server name].[catalog].[owner].[table] syntax but using select * from [linked server name].[catalog].[owner].[table]@oracle_dblink_name syntax from the oracle side throw this error:
ERROR at line 1:
ORA-00933: SQL command not properly ended
I tried some syntax variations, e.g. putting double quotes around the object name without luck. After some hours to find a solution I'm out of idea...
So please if someone had a clue on this it would be very helpfull.
Some info:
Oracle 10g 10.2.0.5 Enterprise Edition x64
Oracle Linux 5.9 Enterprise Edition x64
MSSQL 2008R2 Enterprise x64
Windows Server 2008R2 Enterprise x64
Oracle 11gR2 Enterprise x64 for dg4odbc on MSSQL side
SQL Server Natice Client 10.0 used as ODBC driver

Hi kgronau,
                Maybe I'm not clear in my explanations, sorry.
I want, from Oracle, to query a MSSQL linked server.
Basically I want to do that, if possible:
Oracle --> MSSQL --> linked server --> MSSQL
    ^                                                         ^
    |                                                          |
    ---------------->------------------->--------------------
and maybe have a clue about the syntax to be used.
Knowing that querying the linked server directly form MSSQL is working and querying from Oracle to local MSSQL db is working too.
Using the right syntax should lead me to succes, am I right ? Or maybe its something that cannot be done using oracle dblinks ?
Thanks

Current Security Context Not Trusted When Using Linked Server From ABAP

Hello,
I am experiencing a head-scratcher of a problem when trying to use a Linked Server connection to query a remote SQL Server database from our R/3 system. We have had this working just fine for some time, but after migrating to new hardware and upgrading OS, DBMS, and R/3, now we are running into problems.
The target database is a named instance on SQL Server 2000 SP3, Windows 2000 Server. The original source R/3 system was 4.7x2.00, also on SQL Server 2000 (SP4), Windows 2000 Server. I had been using a Linked Server defined via SQL Enterprise Manager (actually defined when the source was on SQL Server 7), which called an alias defined with the Client Network Utility that pointed to the remote named instance. This alias and Linked Server worked great for several years.
Now we have migrated our R/3 system onto new hardware, running Windows Server 2003 SP1 and SQL Server 2005 SP1. The application itself has been upgraded to ECC 6.0. I performed the migration with a homogeneous system copy, and everything has worked just fine. I redefined the Linked Server on the new SQL 2005 installation, this time avoiding the alias and referencing the remote named instance directly, and it tests out just fine using queries from SQL Management Studio. It also tests fine with OSQL called from the R/3 server console, both when logged on as SAPServiceSID with a trusted connection, and with a SQL login as the schema owner (i.e., 'sid' in lowercase). From outside of R/3, I cannot make it fail. It works perfectly.
That all changes when I try to use the Linked Server within an ABAP application, however. The basic code in use is
EXEC SQL.
   SET XACT_ABORT ON
   DELETE FROM [SERVER\INSTANCE].DATABASE.dbo.TABLE
ENDEXEC.
The only thing different about this code from that before the upgrade/migration is the reference to [SERVER\INSTANCE] which previously used the alias of just SERVER.
The program short dumps with runtime error DBIF_DSQL2_SQL_ERROR, exception CX_SY_NATIVE_SQL_ERROR. The database error code is 15274, and the error text is "Access to the remote server is denied because the current security context is not trusted."
I have set the "trustworthy" property on the R/3 database, I have ensured SAPServiceSID is a member of the sysadmin SQL role, I've even made it a member of the local Administrators group on both source and target servers, and I've done the same with the SQL Server service account (it uses a domain account). I have configured the Distributed Transaction Coordinator on the source (Win2003) system per Microsoft KB 839279 (this fixed problems with remote queries coming the other way from the SQL2000 system), and I've upgraded the system stored procedures on the target (SQL2000) system according to MS KB 906954. I also tried making the schema user a member of the sysadmin role, but naturally that was disastrous, resulting in an instant R/3 crash (don't try this in production!), so I set it back the way it was (default).
What's really strange is no matter how I try this from outside the R/3 system, it works perfectly, but from within R/3 it does not. A search of SAP Notes, SDN forums, SAPFANS, Microsoft's KnowledgeBase, and MSDN Forums has not yielded quite the same problem (although that did lead me to learning about the "trustworthy" database property).
Any insight someone could offer on this thorny problem would be most appreciated.
Best regards,
Matt

Good news! We have got it to work. However, we did it in something of
a backwards way, and I'm sure you'll laugh when you see how it was done. Also, the solution depends upon the fact that the remote server is still using SQL Server 2000, and so doesn't have quite so many restrictions placed upon it for distributed transactions and Linked Servers as SQL Server 2005 now does.
At the heart of the solution is the fact that the Linked Server coming FROM the remote server TO our SAP system works fine. Finally, coupled with the knowledge that using DBCON on the SAP side to the remote server also does actually provide a connection (see Notes 323151 and 738371), we set up a roundabout way of achieving our goal. In essence, from ABAP, we set up the DBCON connection to the remote server, at which point all the Native SQL commands execute in the context of the remote server. From within that connection, we
reference the tables in SAP via the Linked Server defined on the remote
server, as if SAP were the remote server, selecting data from SAP and inserting it into the remote (but apparently local to this connection) tables.
So, to spell it out, we define a Linked Server on the remote server pointing back to the SAP server as SAPSERV, with a SQL login mapping defined on the remote system pointing back to a SQL login in the SAP database. We also define a connection to the remote server from SAP using DBCON, using that remote SQL login for authentication.
Then, in our ABAP code, we simply do something along the lines of
exec sql.
   set connection 'REMOTE'
endexec.
exec sql.
   connect to 'REMOTE'
endexec.
exec sql.
   insert into REMOTE_TABLE
      select * from SAPSERV.SID.sid.SAP_TABLE
endexec.
exec sql.
   commit
endexec.
exec sql.
   disconnect 'REMOTE'
endexec.
This is, of course, a test program, but it demonstrated that it worked,
and we were able to see that entries were appropriately deleted and inserted in the remote server's table. The actual program for use is a little more complex, in that there are about four different operations at different times, and we had to resolve the fact that the temp table SAP_TABLE was being held in a lock by our program, resulting in a deadly embrace, but our developer was able to work that out, and all is now well.
I don't know if this solution will have applicability to any other customers, but it works for us, for now.
SAPSERV, REMOTE, REMOTE_TABLE, and SAP_TABLE are, of course, placeholder names, not the actual server or table names, so as not to confuse anyone.
Best regards,
Matt

How to create a Linked Server from SQL Server 2012 to Postgresql

Hi, I am working on a third party application which is using Postgresql version 9 database and I am trying create a linked server in SQL Server 2012 using the below stored procedure.
EXEC master.dbo.sp_addlinkedserver @server = N'LINKEDSERVERPOSTGRES', @srvproduct=N'PostgreSQL',
@provider=N'MSDASQL', @provstr=N'Driver=PostgreSQL;uid=pguser;Server=pghost;database=pgdatabase;pwd=somepassword'
Error: Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server.
I have no clue if a jdbc provider exists in SQL Server to connect to Postgresql or what the right provider is? Could you please let me know if there's a workaround to achieve this.
Thanks in advance............
Ione

See if this helps
http://www.postgresonline.com/journal/archives/46-Setting-up-PostgreSQL-as-a-Linked-Server-in-Microsoft-SQL-Server-64-bit.html
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

Querying Active Directory via linked server in SQL2012

I'm attempting to create a view in SQL2012 which I can then use in SharePoint 2013. I need a list of the users in an AD group called DeviceAdmins. I got this query to work, but
it only gives me the name of the group DeviceAdmins, not the members of that group. What am I doing wrong?
SELECT
top200
name,telephonenumberFROMOPENQUERY
ADSI,'SELECT
NAME,telephonenumber FROM ''LDAP://CN=DeviceAdmins,OU=security groups,dc=xxx,dc=yyy,dc=com''')

Hi mkrener212,
Based on my knowledge, You can retrieve single-valued attributes like "sn" (surname = last name) or "givenName" and "mail" and so forth, but the SQL-based interface isn't capable of handling attributes like "memberOf" with several values assigned to them.
So I'm afraid you'll have to go another way for this problem - e.g. find and populate the group membership in managed code.
What's more, this is the forum for Directory Services, you can go to the following SQL forum to get more professional help:
http://social.technet.microsoft.com/Forums/en-US/home?category=sqlserver
Regards,
Lany Zhang

SQL 2012 Linked Server connection from SQL 2000

Hi,
Does anyone know if it's possible to create a linked server connection in SQL 2000 to a SQL 2012 instance?
If so, which provider should I use?
Many Thanks,
Phil

Hi Shanky,
I'm afraid you misunderstood my Q. The above posts show how to create a linked server connection FROM SQL2012 --> SQL 2000.
I'm trying to create a linked server connection FROM SQL 2000 --> SQL 2012.
Does anyone know if it's possible?
Many Thanks,
Phil
I guess you dont read posts patiently below link ,which i also posted in my first reply, has details about the same
http://social.msdn.microsoft.com/Forums/en-US/2e02c603-e28d-49eb-b073-548c59732b5d/linked-server-from-sql2012-to-sql2000?forum=sqlsetupandupgrade
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Linked Server Error from SQL2008R2 to SQL2000

I am trying to Execute Query/SP from my local machine which SQL 2008R2 To SQL 2000 32 bit.
Created Linked Server from Local machine to SQL2000 Machine..
Query /SP run fine from SSMS but when I am trying to run through this below script keep giving me error .
I converted Select query into SP
EXEC msdb.dbo.sp_send_dbmail
@profile_name = 'SQL-MailAlerts',
@recipients = '**********',
@query = 'EXEC dbo.QueryResult',
@query_attachment_filename = 'result.csv',
@attach_query_result_as_file = 1,
@body_format = 'text' ;
Error :
Msg 22050, Level 16, State 1, Line 0
Error formatting query, probably invalid parameters
Msg 14661, Level 16, State 1, Procedure sp_send_dbmail, Line 504
Linked servers cannot be used under impersonation without a mapping for the impersonated login.
Basically trying to get Query result from SQL 2000 Database into mail if anyone has better idea let me know.
Thanks
Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach A.Shah

Maybe you should read the posts before you reply? Logicinisde runs DB mail on SQL 2008R2, but is trying to retrieve data from SQL 2000 instances.
SQL 2000 may be out of support, but that will not prevent users from keeping their instances around as long as needed. In some cases they may have no choice, because they are running a third-party system which does not support later versions of SQL Server.
I have gathered that this is particularly common in the healthcare industry in the US.
Hi Erland Sommarskog,
Thanks for your suggestion, the scenario which you post is really to take into consideration. I suggest our customer upgrading the SQL Server version for helping resolve his issues which may be encountered on the SQL Server 2000. Thanks for your understanding.
Thanks for your post again.
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

How could I create a "Linked Server" link from SQL Server 2008R2 64-Bit to Oracle Database 11.2 64-Bit?

How could I create a "Linked Server" link from SQL Server 2008R2 64-Bit to Oracle Database 11.2 64-Bit?
Let's say the SQL Server and Oracle Database are in the same Company Internet Network.
I have the code, but I do not know how to use it. Such as what is System DSN Name? Where could I get it. What does it look like?
Do I need to install any Oracle Client Software in order to link from SQL Server to Oracle? Or SQL Server has the built-in drivers installed already that I can directly create a Linked Server from SQL Server to Oracle?
I need to know details. Thanks.
USE master
go
EXEC sp_addlinkedserver
     @server  = '{Linked Server Name}'
    ,@srvproduct = '{System DSN Name}'
    ,@provider  = 'MSDASQL'
    ,@datasrc  = '{System DSN Name}'
EXEC sp_addlinkedsrvlogin
     @rmtsrvname = '{Linked Server Name}'
    ,@useself  = 'False'
    ,@locallogin = NULL
    ,@rmtuser  = '{Oracle User Name}'
    ,@rmtpassword = '{Oracle User Password}'

You need an OLE DB provider for Oracle. There is one that ships with Windows, but it only supports very old versions of Oracle. Oracle has an OLE DB provider that you can use. I don't know if it's part of Oracle Client or how it is bundled.
You should not use MSDASQL or any DSN.
Erland Sommarskog, SQL Server MVP, [email protected]

Need to pull the data from one server to another server in SSMS using linked server

Hi, I have store proc which will take the parameters passed to it and store it in a table in that server. Now, this table data has to be pulled to another server table which is of same structure. But I need to do that in the same store proc which is in
first server. I have searched in online but could not figure it how to link connection between these two servers and pull data from the first sever to the second. Can anyone please help

You can setup a linked server from Server A to Server B. Then you will be able to query server B from Server A.
eg: Assume you have a database test in Server B which has a table sample. From server A you could run this query to pull details.
Select * from ServerB.test.dbo.sample.
http://msdn.microsoft.com/en-us/library/ms188279.aspx
http://msdn.microsoft.com/en-us/library/ff772782.aspx#SSMSProcedure
You also have other options like distributed queries (openquery), check this blog
http://blog.sqlauthority.com/2007/10/06/sql-server-executing-remote-stored-procedure-calling-stored-procedure-on-linked-server/
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

SQL to Oracle Linked Server

I am trying to create a linked server from SQL2000 to Oracle9i.
i have done followings:
Install Oracle9i client on sql server machine.
Create a tnsname entry for my oracle database.
Created a linked server using following query:
exec sp_addlinkedserver 'ORA_HIPPOCRT',
'Oracle', 'MSDAORA', 'HIPPOCRT'
exec sp_addlinkedsrvlogin 'ORA_HIPPOCRT',
false, NULL, 'HR', 'password'
But when I query the data as follows:
SELECT * FROM ORA_HIPPOCRT..HR.EMPLOYEES
I get following errors:
Server: Msg 7399, Level 16, State 1, Line 1
OLE DB provider 'MSDAORA' reported an error.
[OLE/DB provider returned message: Oracle client and networking components were not found. These components are supplied by Oracle Corporation and are part of the Oracle Version 7.3.3 or later client software installation.
Provider is unable to function until these components are installed.]
OLE DB error trace [OLE/DB Provider 'MSDAORA' IDBInitialize::Initialize returned 0x80004005: ].
What I am doing wrong?

I can get this to work using OPENQUERY() i.e.
select * from OPENQUERY(andyh, 'select * from TRAINDB.LINKEDSERVERDATATYPETEST')
To me though this has bodge written all over it.
Anyone out there with advise for me?
thanks.

Error when creating a linked server to IBM iSeries AS/400

I am migrating databases from SQL Standard 2005 (32 bit) to SQL Standard
2012 (64 bit) and getting errors when I create the needed Linked Servers to our IBM as/400. I scripted the as400 linked server from the 2005 server and created it on the 2012 server:
EXEC master.dbo.sp_addlinkedserver @server = N'AS400', @srvproduct=N'DB2 UDB for iSeries', @provider=N'MSDASQL', @datasrc=N'AS400'
EXEC master.dbo.sp_addlinkedsrvlogin @rmtsrvname=N'AS400',@useself=N'False',@locallogin=NULL,@rmtuser=N'USER_NAME',@rmtpassword='PSSWD'
(plus various sp_serveroptions)
I then verified that the MSDASQL Provider "Allow Inprocess" was checked and the Linked Server is listed as using the provider but when I try to view the objects under the "AS400" Linked Server I get an error saying: Cannot initialize the
data source object of OLE DB provider "MSDASQL" for linked server "AS400". (Microsoft SQL Server, Error: 7303)
I was told to download and install OLEDB provider for DB2. I downloaded DB2OLEDBV4 but when I try to install it I try to install it I get a OK Box saying: "Microsoft OLE DB Provider for DB2 requires the Microsoft SQL Server 2008 or later
version. Ensure that this version is fullfilled before installing Microsoft OLE DB Provider for DB2." when I click OK, I get "Setup was interrupted before Microsoft OLE DB Provider for DB2 could be completely installed" and the install
exists. I am installing on SQL 2012!
Can anyone please advise...

Hi,
Based on your description, we know that you got an error when you installed the OLEDB provider for DB2. Microsoft OLE DB Provider for DB2 V4.0 is needed If you use SQL Server 2008 R2 or SQL Server 2012 to connect to IBM DB2 databases.When you install the
OLEDB provider for DB2 V4.0, we need to make sure that the system meets the following requirements:
• Windows Server 2008 R2 SP1 or Windows 7 SP1 or Windows Server 2008 SP2.
• Microsoft SQL Server 2012 (Enterprise, Developer or Evaluation Edition) or Microsoft SQL Server 2008 R2 (Datacenter, Enterprise, Developer or Evaluation Edition) is installed.
• Microsoft .NET Framework 4.0.
As your post,it seems that you have installed SQL Server 2012 Standard Edition,this edition is not supported by Microsoft OLEDB Provider for DB2 V4.0. I recommend you to upgrade the standard edition to enterprise edition and reinstall the OLEDB Provider.You
can try this method and if you have any questions,please feel free to revert.
For more detailed information, you can review the following link.http://msdn.microsoft.com/en-us/library/hh873008(v=sql.110).aspx
Thanks
Lydia Zhang

SQL 2000 LINKED SERVER ERROR 7303 WITH SQL 2012 ON WINDOWS SERVER 2012 R2

Hi all,
I have a problem with SQL Server 2012 and a linked server for SQL 2000 database.
System specification:
Windows server 2012 64 bit
SQL SERVER 2012 64 bit
REMOTE SERVER SQL 2000 32 bit
I've installed sql native client 32bit,create a SYSTEM DSN odbc connection with "SQL Server" driver named "MYSERVER".
Create a linked server with the query below in SQL 2012:
EXEC master.dbo.sp_addlinkedserver @server =N'MYSERVER', @srvproduct=N'MYSERVER', @provider=N'MSDASQL', @datasrc =N'MYSERVER', @location=N'System';
EXEC master.dbo.sp_addlinkedsrvlogin @rmtsrvname=N'MySERVER',@useself=N'True',@locallogin=NULL,@rmtuser=NULL,@rmtpassword=NULL
GO
but when i browse the linked server i receved error 7303.

You need 64-bit MSDASQL. It is the bitness of the server you are connecting from that matters. 64-bit executables cannot hook into 32-bit DLL.
However, I suspect that you will not get things to work anyway. At least I have not seen anyone this far who has been able to set up a linked server from SQL 2012 to SQL 2000. I know that when I tried this, the following providers had this result:
SQLNCLI11 - does not support connections to SQL 2000.
SQLNCLI10 - failed with some obscure message that I don't recall.
SQLNCLI - Don't recall that the problem was here.
SQLOLEDB - SQLOLEDB is always replaced with the most recent version of SQLNCLI, so this fails because of lack of support.
I don't think I got through all version of the ODBC drivers, though.
Erland Sommarskog, SQL Server MVP, [email protected]

Linked Server error: Login Failed for user 'NT AUTHORITY\ANONYMOUS LOGON' between sql server 2005 32 bit and sql server 2012 64 bit

Hi All,
Here the linked server is created between sql server 2012 64 bit and sql server 2005 32 bit. I am getting the below error when i try to access linked server from third server. I have created linked from Instance 1 to Instance 2. When i access it from
instance 3 i am getting the below error. SPN setting has been done between these 2 servers. Also the option 'Trust the delegate' is enabled for the both the service account.
'Login Failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
Appreciate your quick response.
Vikas.M.S

Hello,
Please read the following resources:
http://www.databasejournal.com/features/mssql/article.php/3696506/Setting-Up-Delegation-for-Linked-Servers.htm
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/ea26de43-4c6b-4991-86d7-e1578f107c92/linked-server-login-failed-for-user-nt-authorityanonymous-logon?forum=sqldataaccess
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Linked server from SQL2012 to SQL2000

Similar Messages

Maybe you are looking for