Home
%3CLINGO-SUB%20id%3D%22lingo-sub-662656%22%20slang%3D%22en-US%22%3ELesson%20Learned%20%2387%3A%20Connecting%20from%20SQL%20Server%202008%2FR2%20to%20Managed%20Instance%20using%20Linked%20Server.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-662656%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHello%20Team%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20you%20know%2C%20the%20support%20of%20SQL%20Server%202008%20and%20SQL%20Server%202008%20R2%20is%20approaching%20to%20the%20end%20and%20some%20customers%20are%20using%20Linked%20Server%20to%20connect%20to%20Azure%20SQL%20Managed%20Instance%20for%20sending%20or%20retrieving%20data.%20We%20found%20a%20particular%20error%20message%20here%20and%20we%20explain%20how%20to%20fix%20it.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20this%20situation%20our%20customer%20tried%20to%20send%20data%20from%20SQL%20Server%202008%20to%20Azure%20SQL%20Managed%20Instance%20using%20linked%20server%20but%20they%20got%20the%20error%20messages%20at%20the%20moment%20of%20the%20definition%2C%20using%20multiple%20providers%20Microsoft%20OLE%20DB%20Provider%20for%20SQL%20Server%20or%20SQL%20Server%20Native%20Client%2010.0%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EServer%20name%20not%20found%3C%2FLI%3E%0A%3CLI%3EServer%20name%20needs%20to%20be%20the%20same%20in%20the%20connection%20string%3C%2FLI%3E%0A%3CLI%3EServer%20name%20cannot%20be%20determined.%20It%20must%20appear%20as%20the%20first%20segment%20of%20the%20server's%20dns%20name).%20etc..%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22text-align%3A%20center%3B%22%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20615px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F116854i9DC55F3505F2EACA%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Capture.PNG%22%20title%3D%22Capture.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20workaround%20used%20to%20be%20able%20to%20connect%20was%20specifying%20the%20connection%20string%20of%20Azure%20SQL%20Managed%20instance%26nbsp%3Bin%20the%20provider%20string%26nbsp%3Bsection%20of%20the%20linked%20server%20definition%20without%20password%20parameter.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EEnjoy!!!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-662656%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20you%20know%2C%20the%20support%20of%20SQL%20Server%202008%20and%20SQL%20Server%202008%20R2%20is%20approaching%20to%20the%20end%20and%20some%20customers%20are%20using%20Linked%20Server%20to%20connect%20to%20Azure%20SQL%20Managed%20Instance%20for%20sending%20or%20retrieving%20data.%20We%20found%20a%20particular%20error%20message%20here%20and%20we%20explain%20how%20to%20fix%20it.%3C%2FP%3E%3C%2FLINGO-TEASER%3E

 

 

Hello Team,

 

As you know, the support of SQL Server 2008 and SQL Server 2008 R2 is approaching to the end and some customers are using Linked Server to connect to Azure SQL Managed Instance for sending or retrieving data. We found a particular error message here and we explain how to fix it.

 

In this situation our customer tried to send data from SQL Server 2008 to Azure SQL Managed Instance using linked server but they got the error messages at the moment of the definition, using multiple providers Microsoft OLE DB Provider for SQL Server or SQL Server Native Client 10.0

 

  • Server name not found
  • Server name needs to be the same in the connection string
  • Server name cannot be determined. It must appear as the first segment of the server's dns name). etc..

 

Capture.PNG

 

The workaround used to be able to connect was specifying the connection string of Azure SQL Managed instance in the provider string section of the linked server definition without password parameter.

 

Enjoy!!!