Best Practice to get data from on-premises SQL Server.

%3CLINGO-SUB%20id%3D%22lingo-sub-2541020%22%20slang%3D%22en-US%22%3EBest%20Practice%20to%20get%20data%20from%20on-premises%20SQL%20Server.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2541020%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EHow%20do%20I%20get%20data%20from%20on-premises%20SQL%20Server%20which%20connected%20to%20my%20Azure%20with%20VPN%20Site-To-Site%3F%26nbsp%3B%20I%20have%20tried%20'direct'%20(set%20the%20IP%20on-premises%20SQL%20Server)%20connection%20in%20linked%20service%2C%20but%20failed%20to%20connect.%26nbsp%3B%20The%20error%20message%3A%20%3CEM%3ECannot%20connect%20to%20SQL%20Database%3A%20x.x.x.x%5Cinstance_name%2C%20Database%3A%20db1%2C%20User%3A%20user01.%20Check%20the%20linked%20service%20configuration%20is%20correct%2C%20and%20make%20sure%20the%20SQL%20Database%20firewall%20allows%20the%20integration%20runtime%20to%20access.%20A%20network-related%20or%20instance-specific%20error%20occurred%20while%20establishing%20a%20connection%20to%20SQL%20Server.%20The%20server%20was%20not%20found%20or%20was%20not%20accessible.%20Verify%20that%20the%20instance%20name%20is%20correct%20and%20that%20SQL%20Server%20is%20configured%20to%20allow%20remote%20connections.%20(provider%3A%20SQL%20Network%20Interfaces%2C%20error%3A%2026%20-%20Error%20Locating%20Server%2FInstance%20Specified)%2C%20SqlErrorNumber%3D-1%2CClass%3D20%2CState%3D0%2C%20Activity%20ID%3A%207c20c940-0415-4b19-9c19-d30692aeeb16.%3C%2FEM%3E%3C%2FP%3E%3CP%3EI%20already%20tested%20the%20same%20configuration%20with%20DBeaver%20(SQL%20client%20tool)%20in%20one%20of%20my%20VM%20in%20my%20Azure%2C%20and%20successfully%20connected.%26nbsp%3B%20I%20have%20checked%2C%20firewall%20on-premises%20do%20not%20blocking%20any%20IP%20from%20Azure.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20what%20is%20the%20best%20practice%20to%20get%20data%20from%20SQL%20Server%20on-premises%3F%26nbsp%3B%20Is%20using%20Self%20Hosted%20Integration%20Runtime%20the%20only%20way%20to%20achieve%20this%20goal%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20in%20advance.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2541020%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20Data%20Factory%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAzure%20Integration%20Runtime%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Frequent Visitor

Hi,

How do I get data from on-premises SQL Server which connected to my Azure with VPN Site-To-Site?  I have tried 'direct' (set the IP on-premises SQL Server) connection in linked service, but failed to connect.  The error message: Cannot connect to SQL Database: x.x.x.x\instance_name, Database: db1, User: user01. Check the linked service configuration is correct, and make sure the SQL Database firewall allows the integration runtime to access. A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified), SqlErrorNumber=-1,Class=20,State=0, Activity ID: 7c20c940-0415-4b19-9c19-d30692aeeb16.

I already tested the same configuration with DBeaver (SQL client tool) in one of my VM in my Azure, and successfully connected.  I have checked, firewall on-premises do not blocking any IP from Azure.

 

So what is the best practice to get data from SQL Server on-premises?  Is using Self Hosted Integration Runtime the only way to achieve this goal?

 

Thanks in advance.

0 Replies