I know this has been talked about again, and again.. but
This is what i got..
1. 2x Windows 2003 Ent servers.. attached to a dell powervault 220s
storage array that has
a. 3x arrays, 1 for the the quorom, 1 for each clusternode's
data disk
2. SQL 2005 Installed with a default instance named lets say sql1 as
the virtual servername, and it's IP address
What the developers said they need / want is another "default" instance,
or something that from there programs just call a single name instead of
having to use the virtualservername\instance name so something more like
sql2, is this possible... i have been reading that it isn't.. that you will
end up with virtualservername\instance for anything other then the default
instance. Also i have been reading that you can alias the
virtualservername\instance in DNS with a SRV record, but i dont seem to have
a type of _sql or something listed in the srv records available to me on my
2000 AD,,, what am i missing to make this work the way the developers needs?
Please help me, thanks!
So what they're saying is they need sql2 instead of sql1\B? Have them go to
the CFO and cost justify why buying another cluster is worth them not having
to type those two extra characters. Let us know what he says.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Jeff Pancrazio" <jpancrazioNO@.SPAMgmail.com> wrote in message
news:uRT%23JEmjHHA.568@.TK2MSFTNGP02.phx.gbl...
>I know this has been talked about again, and again.. but
> This is what i got..
> 1. 2x Windows 2003 Ent servers.. attached to a dell powervault 220s
> storage array that has
> a. 3x arrays, 1 for the the quorom, 1 for each clusternode's
> data disk
> 2. SQL 2005 Installed with a default instance named lets say sql1
> as the virtual servername, and it's IP address
> What the developers said they need / want is another "default" instance,
> or something that from there programs just call a single name instead of
> having to use the virtualservername\instance name so something more like
> sql2, is this possible... i have been reading that it isn't.. that you
> will end up with virtualservername\instance for anything other then the
> default instance. Also i have been reading that you can alias the
> virtualservername\instance in DNS with a SRV record, but i dont seem to
> have a type of _sql or something listed in the srv records available to me
> on my 2000 AD,,, what am i missing to make this work the way the
> developers needs?
> Please help me, thanks!
>
|||Roger Wolter[MSFT] wrote:
> So what they're saying is they need sql2 instead of sql1\B? Have them
> go to the CFO and cost justify why buying another cluster is worth them
> not having to type those two extra characters. Let us know what he says.
>
Additionally: unless the developers are hard-coding the name of the
server into their apps (which would be the height of stupidity, IMO),
the 'virtualserver\instance' name should be transparently
interchangeable with the default instance's 'server' name.
My organization has several apps that were originally implemented on
individual hosts using the default instance on each host. We ponied up
for some big hardware to create a cluster, and now we run several named
instances on an active/active cluster without any special
support/assistance from the developers: we simply substituted the
'servername' with 'server\instance' in all the configuration locations
(whether it was an ODBC DSN, registry string or INI file) to get it to
'just work.'
AFAIK, this is supported because of the SQL Server driver, not the
creative coding of the application developer.
No comments:
Post a Comment