Is it possible to use azure sql hybrid join on a named instance?

Can't find a definitive answer or get it to work. The site says, "To use a local SQL Server or SQL Server Express database with hybrid connectivity, TCP / IP must be enabled on a static port . Instances on SQL Server use static port 1433 by default, whereas named instances do not."

http://azure.microsoft.com/en-us/documentation/articles/web-sites-hybrid-connection-connect-on-premises-sql-server/

My installation of a named IS instance on a static port (1555) as described here:

http://blogs.msdn.com/b/arvindsh/archive/2012/09/08/how-to-assign-a-static-port-to-a-sql-server-named-instance-and-avoid- a-common-pitfall.aspx

I have a hybrid connection configured on azure portal with port 1555 and it shows as Instance Connected.

In the application connection string, I specify the instance name and port in the same way as if the application were in place, which works when running locally. (server \ instance, 1555)

I have opened all relevant firewall ports, but when running the application from azure, I get a standard connection error. A network related or instance specific error occurred while establishing a connection to SQL Server. The server was not found or was not available. Verify that the instance name is correct and configure SQL Server for remote connection. (Provider: TCP Provider, Error: 0 - No such host is known.)

So this is a named instance on a non-standard port supported for hybrid connections, and if so, is the connection string in the standard format: server \ instanceName, port #

thank

+3


source to share


1 answer


This is an old post, so it doesn't seem to be relevant anymore. But in case someone finds this useful ... Yes, you can use a named instance on a non-standard port for hybrid connections, I have several connections similar to this setup. For reference, the connection string should be in the format

Driver = {SQL Server}; Server = SERVER_NAME.DOMAIN.com \ INSTANCE, PORT; Database = DATABASE_NAME; UID = USERNAME; PWD = PASSWORD



I found that it didn't work (for me) unless I fully qualified the server name with the domain.

+3


source







All Articles