Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 882
  • Last Modified:

Problem Understanding sp_addlinkedserver

I know this should be straight forward, but cannot get it to work...

Scenario...
2 servers, both running SQL 2005
     Server A
     Server B

I need to link to Server B from Server A to run queries

I am assuming sp_addlinkedserver to be the way to go....so....

I executed the following query from Server A...(obviously the names have been changed to protect the innocent)

exec sp_addlinkedserver
      @server='myFriendlyName',
      @provider='',
      @srvproduct='',
      @datasrc='actualServername',
      @catalog='actualDBName'

Response was "Command(s) completed successfully."

I then try to run a query as such....

SELECT *
FROM myFriendlyName.[actualDBName].[tableName]
WHERE description like '%stuff%'

Intellisense doesnt like it, but I ran it anyway and got the following error....

Msg 208, Level 16, State 1, Line 6
Invalid object name 'myFriendlyName.actualDBName.tableName'.



Response
0
JayFromPep
Asked:
JayFromPep
  • 3
  • 3
1 Solution
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
SELECT * FROM myFriendlyName.[actualDBName].dbo.[tableName]WHERE description like '%stuff%'
0
 
JayFromPepAuthor Commented:
Thanks Angel!

got a bit farther and new error....

Msg 7403, Level 16, State 1, Line 6
The OLE DB provider "" has not been registered.
0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
you have to tell that the remote is sql server also:
http://msdn.microsoft.com/en-us/library/ms190479.aspx

exec sp_addlinkedserver
      @server='myFriendlyName',
      @provider='',
      @srvproduct='SQL',
      @datasrc='actualServername',
      @catalog='actualDBName'

Open in new window

0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
JayFromPepAuthor Commented:
OK, new stuff....

Here is what I used to create the linkedserver....


exec sp_addlinkedserver
      @server='myFriendlyName',
      @provider='SQLNCLI',
      @srvproduct='',
      @datasrc='actualServerName\actualDBName'

Worked....but now I am getting login errors....

OLE DB provider "SQLNCLI10" for linked server "myFriendlyName" returned message "Login timeout expired".
OLE DB provider "SQLNCLI10" for linked server "myFriendlyName" returned message "A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.".
Msg 65535, Level 16, State 1, Line 0
SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].
0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
article to start troubleshooting the connection:
http://www.experts-exchange.com/A_1881.html
0
 
JayFromPepAuthor Commented:
hmmm....went through the doc, but no luck.  username and password is good (as dbo), remote connections are allowed.

Perhaps there is something else I am forgetting in sp_addlinkedserver command....

exec sp_addlinkedserver
      @server='myFriendlyName',
      @provider='SQLNCLI',
      @srvproduct='',
      @datasrc='actualServer\actualDB',
      @provstr='User ID=username;password=password'
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now