DQSInstaller.exe is pretty limited in its options and as such does not provide any option to redirect your DQS installation on a seperate instance of SQL server. Further it is hardcoded for now to install the DQS components on the default instance (MSSQLSERVER) of the SQL Server 2012 with the default Instance ID (MSSQLSERVER).
What this mean is if you change the InstanceID of your installation during the setup of SQL Server, it will not allow you to install the DQS throwing an error that it was not able to connect to the specified server. Youc can learn more about it from here.
Well what do you do then, do you remove and reinstall the SQL Server ?
If you happen to be one of them liek me who has changed the instanceID of your default installation then you can use the following workaround to recify the same.
The DQSInstaller.exe uses the combination of the servername and the InstanceID to install the DQS components.
For example if you are using MYServer as the server name and InstanceID as MSSQSSERVER12 then it will search for MyServer\MSSQLSERVER12.
What you can do to workaround this is create an alias with the name as MyServer\MSSQLSERVER12 and pointing to the default instance ie. just the server name. A sample is shown below.
Note that you will have to enable the TCP/IP protocol for bothe the client and the server next.
I had the SQL Server 64 bit version installed and the DQSInstaller.exe is a 64bit code so creating an alias for only the 64-bit client is fine. I am not sure if the 32bit version of the SQL Server will have 32 bit DQSinstaller on it...but nevertheless you can then create the alias of the 32-bit clietn as well.
I think you can also direct the DQSInstaller.exe to the right instance name with the switch...
The switch is shown by the -? help on the command line tool.
Such as these commands, the first for default instance, the second for named instance Instance1.
cd "C:\Program Files\Microsoft SQL Server\MSSQL11.InstanceID\MSSQL\Binn\"
DQSInstaller.exe -instance MSSQLServer
DQSInstaller.exe -instance Instance1
As your posts correctly describes, the installed may pick up the wrong instance name if the InstanceID (ie. the folder name) is different than the instance itself, and the workaround alias should work well too.
Well seems like the switch is new, as it did not exist in the release version I was using when I installed DQS and ran the DQSInstaller.exe. Infact I searched over the documentation for the commad line tool and there was no provision to install it on a different instance.
So thanks for keeping me updated on this. Seems like the provision has been added now, unless I missed something.
Here is my situation
When I start SSMS I connect to instance that appears as HPWINDOWS8ONE in the drop down selection.
If I connect to (local) I connect to the same database instance.
All of the files (data, log, etc) are under a directory C:\Program Files\Microsoft SQL Server\MSSQL.MSSQLSERVER2012_DEV
I have tried every combination of -instance and everyone returns same message 'unable to connect to server ---'
If you have a solution, please email me at firstname.lastname@example.org.