October 1, 2012 at 12:23 pm
Hi I have installed SQL Server 2008 (F1SQL) with two named instances (DEV, QA) and this server is configured for mixed mode authentication.
Now when I am connecting to this server, it is not allowing connection with server name as F1SQL\DEV, F1SQL\QA but allowing connection with F1SQL\DEV,1433, F1SQL\QA,1433 respectively .
I dont want to specify the port numbers while I connect to this database instance, so I tried creating an alias F1SQLDEV for the F1SQL\DEV using SQL server Configuration manager and it didn't work, so can some one please help me out.
October 1, 2012 at 1:01 pm
What/where are you connecting from? Management Studio? Linked servers? Something in your application(s)?
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
October 1, 2012 at 1:10 pm
Do you have the SQL server browser service running?
October 1, 2012 at 1:20 pm
I am connecting from the Management studio
October 1, 2012 at 1:21 pm
I have SQL Server Browser services running
October 1, 2012 at 1:21 pm
Make sure SQL Server Browser service is running correctly.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
October 1, 2012 at 2:33 pm
And make sure UDP port 1434 is open from your workstations to your server (check Windows firewall settings and other network firewalls).
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
October 1, 2012 at 4:53 pm
if you don't have any database attached with that instance then try to use repair option.........
October 2, 2012 at 2:21 am
If you are able to make connection with using port no and without port you are not then browser service is not running and if it looking running then port 1434 is not open.Please check port 1434 is open or not.
October 2, 2012 at 3:13 am
One option is to configure the two instances with their own IP addresses and then you can use port 1433 on both.
This way you can use DNS for all your connection strings, odbc and so on and then you don't have to mess with aliases.
Using server\instance or random portnumbers in connectionstrings is administrative/migration hell..
So I've set a standard for the DNS entries:
SQL-ApplicationName.company.local
SQL-Databasename.company.local
And I use this for ALL SQL connections , this way it is easier to migrate/move in the future (just change IP for the host entry).
Also everything is documented in the DNS.
There are some things to think about when setting this up, reply to this if you are interested.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply