March 12, 2012 at 2:40 pm
I have a windows 2008 server cALLED QNXTDB02STL. I installed a sql 2008 R2 instance on it and named the instance
QNXTSQLSTLTST01. Install complere works fine. however 3rd party app and sql tools will only connect to
QNXTDB02STL\QNXTSQLSTLTST01. I need just the instance name to connect for the 3rd party app. Can't find a config or way to address this. In the services and the configuration it has just QNXTSQLSTLTST01, but I can not connect to the instance with this name. Any ideas or workaround?
March 12, 2012 at 2:47 pm
Two steps..
Change the port that the named instance is listening on to 1433.
Add a DNS CNAME record for the name pointing at the QNXTDB02STL name.
OR
Better answer, uninstall, re-install as a default instance
Add a DNS CNAME record for the name pointing at the QNXTDB02STL name.
OR
EVEN Better answer, uninstall, re-install as a default instance
Change the connection to the machine's name..
CEWII
March 12, 2012 at 2:57 pm
Firstly the app is at fault. It appears not to be able to cope with a named instance.
I wonder if setting up a server alias of QNXTSQLSTLTST01 for the named instance would work
---------------------------------------------------------------------
March 12, 2012 at 2:59 pm
whEN i DID THE INSTALL i TOLD IT TO USE NAMED INSTANCE, SQL SERVER CAN'T HAVE SAME NAME AS COMPUTER
March 12, 2012 at 2:59 pm
....or have I read this wrong and the configuration file just needs changing to QNXTDB02STL\QNXTSQLSTLTST01
---------------------------------------------------------------------
March 12, 2012 at 2:59 pm
No, it probably won't..
The tools by default look at port 1433 for TCP/IP and a named instance by default will NEVER be there. you have to force it there.
As a wider question, why did you install as a named instance?
CEWII
March 12, 2012 at 3:03 pm
Can't change config file. Long story short, trying to disprove that Virtual SQL Server is not issue. TO make life easier needed a physcial box with a different name, instance name is all application is looking for. Physical server could not have same name as virtual
March 12, 2012 at 3:09 pm
did you try specifying the specific port in the connection string?
for exmaple, if you changed the dynamic listeninc port below from 1711 (or whatever yours currently is) to port 14330
the connection string would be [server][comma][port]
like this:
data source=QNXTDB02STL\QNXTSQLSTLTST01,14330;
initial catalog=PROD_COPY;
Connect Timeout=600;
Trusted_Connection=True;
Application Name=MyApplication.SQLConnection.exe;
Lowell
March 12, 2012 at 3:36 pm
You can't name the named instance the same name as the computer but by default a default instance would be the same name.
CEWII
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply