Hello Thwacksters
Does any one know if the SolarWinds Configuration Wizard able to use SQL server alias for the SQL server connection string? I've not been able to configure this myself.
Thanks
Brand new install or connecting to an existing database ?
I have usually used the Domain then ComputerName to directly connect to a SQL server or to a SQL Listener for a SQL Cluster. I see no reason why a DNS alias would not work. Permissions issues? The account needs to be DB_Owner at a minimum after the installation but the initial install may require SA unless you have pre-created blank databases to attach to. The initial install creates new databases by default. Some possible thoughts.
Hey Bob,
Existing install. I am trying to change the SQL Server value under Database Settings in the Configuration Wizard to a SQL Alias instead of the <ServerName>\<InstanceName> format.
I have no issues with actually getting the configuration wizard to work if I use the <ServerName>\<InstanceName> format, but it seems like it won't accept an alias.
I agree it should "just work", but sadly it doesn't. If I test the connection with a .UDL file it tests successfully.
I've created the alias using the cliconfg.exe tool.
Maybe it has something to do with the automatic SqlConnectionFormater that the Config Wizard is doing?
Because using the corrected string in the .UDL file doesn't work as well:
What port is your SQL instance listening on?
When you set up a named instance, <ServerName>\<InstanceName>, the instance by default listen on a random tcp port. Whan an application tries to connect to a named instance, the application asks the SQL Browser service on port UDP/1434, what port that instance is listening to. Then the application can connect to the correct port.
If you have a DNS alias, the SQL Browser service does not know what instance you are asking for. Giving no reply and the application will try to default TCP/1433.
So, make sure your instance is listening on TCP/1433 if you want this to work, OR write this in your server field: "SolarWindsOrionTest,50001" if 50001 is your listening port. And yes, you have to change the port on your instance so it uses a static port, otherwise it will change after next restart.
Can this be the issue?
Hi Lofstrand
Thank you for taking time to give your thoughts on this matter. And I agree that it very well could've been the issue, but looking at the configuration for the instance it seems to be listening on 1433. The other instance behind the greenbox, is not listening on anything, so it can safely be ignored.
Am I misunderstanding, or does this look OK to you as well?
