Does anyone have a tried and true method to push an alias for a SQL Server out to Clients in a non-domain environment?
asked Sep 28 '10 at 08:30 AM in Default
Looks like I found something...
One workaround is to try the following: Make a REG file that creates a REG_SZ value under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo. The name of the value is the alias and the value is a comma-separated string with the NET Library name, IP (or Server Name), and Port.
Assume we have applications connect to SQLTest as the dB server.
To point to the DEV instance the REG value of SQLTest might be: DBMSSOCN,192.168.1.13,1433 And for QA it might be: DBMSSOCN,192.168.1.13,2112
The name doesn’t change for the Client, they are always accessing SQLTest, but the request is sent to a different port on the same dB box.
The changes can be pushed via batch file, or PowerShell.
We just create DNS alias. If have our DNS team create them for us. We also have the ability to create VIP's (virtual ip addresses). Typically we just use a friendly name serverxyz.domain.com and have it resolve the IP address of the SQL Server. Works great. You still have to specify the named instance or port number for the named instance in the connection.
answered Sep 28 '10 at 08:33 AM