Personally, I prefer all named instances. It makes explaining connection
strings to the dev team a much simpler task since they all look alike.

Signature
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
Hi
It also makes it "harder" to connect to the wrong instance. You have to know
which instance you are connecting to. Those drop table scripts that people
like to use tend to cause havoc when they run it against the wrong instance.
Regards
--------------------------------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
> Personally, I prefer all named instances. It makes explaining connection
> strings to the dev team a much simpler task since they all look alike.
[quoted text clipped - 9 lines]
> > thanks a lot !
> > Rubens
Mike Hodgson - 27 Feb 2005 22:27 GMT
I agree with Mike & Geoff. All my clustered SQL instances have always
been named instances. Technically there are no disadvantages I can
think of to having both instances being named instances and the
advantages are basically in the category of "less confusing".
--
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@mallesons.nospam.com |* W* http://www.mallesons.com
Mike Epprecht (SQL MVP) wrote:
>Hi
>
[quoted text clipped - 36 lines]
>
>