Connecting to Named Microsoft SQL Server Instances
Originally published on 07-21-2011 09:50 AM
One feature of the Microsoft SQL Server relational database management system is the ability to install multiple named instances on the same host computer. When you take this approach, you give each instance a unique name. You can then use either dynamic or static TCP/IP port assignments. In order to get full advantage from the multiple named instances, you must also install and run theSQL Server Browser Serviceon the same computer on which the multiple database instances are installed.
Whether the browser service is installed and running affects how you refer to each instance when configuring an expressor Database Connection.
If the browser service is running, you reference both the computer and instance names when specifying the Host connection value. For example, if the host computer is namedMYSERVERand the database instance is namedSQLEXPRESS, you would enterMYSERVER\SQLEXPRESSfor the Host connection value and leave the Port connection value empty.
If the browser service is not running, you reference only the computer name when specifying the Host connection value and enter the TCP/IP port number used by this database instance into the Port connection value.
If the database instances are using static TCP/IP port number assignments, you most likely already know the port number assigned to each instance.
If the database instances are using dynamically assigned TCP/IP port numbers, you must obtain the current port assignment. This information is available from the SQL Server Configuration Manager; open the Properties window for the TCP/IP protocol of the desired instance and note the value assigned to the TCP Dynamic Ports entry in the IPAll grouping.
After migrating from Qlik Sense Cloud business to Qlik Sense business, I haven't been able to connect succesfully to the desire microsoft sql server instance.
At the beginning I thought that the problem happenned because of my firewall, since the change of services (qlik sense) could've come with a change of location, so I check that all the IPs were white-listed. Nothing change.
In the qlik sense business space I'm using the same server and parameter that I use to connect to in the qlik sense cloud business space and it does not allow me to do it.
I'm connecting to a SQL server 2008 R2 server version, did compatibility change?