July 17, 2008 at 1:21 pm
I have a new SQL Server 2005 failover cluster created and published to AD...
Current Setup:
I have a standalone instance, within our code, we connect to AD, get the database and then find the server that we connect to. This works great as long as it isn't clustered.
What i want to do:
In the future I'd like to use clustered servers for redundancy using the same dynamic connection string system we are using in the current setup.
The Problem:
The problem i am having right now is that when you publish to AD, it publishes the active node and not the cluster name. I can't connect to the active node; I must connect to the cluster name.
Question:
Is there something in AD i can get the cluster name from that is attached to the SQL Server Database or Instance that was publised? From what i have seen there isn't...
July 18, 2008 at 1:58 pm
So has anyone else had this problem or does everyone just use config files? (I'm against config files because the number of them (X applications on Y number of servers) and keeping them all in sync - I'd rather use AD so i don't have to do anything...) =D
If you don't use AD, what other methods do you use?
July 20, 2008 at 1:18 am
from memory i'm certain the cluster name is published into AD, search AD for the cluster name and check the container it is in
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 29, 2008 at 2:04 pm
I haven't found anything - i just see the published node name (which is on the PC account for that node - the other node isn't published so if it fails over it will fail)
Unless i'm publishing incorrectly.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply