It all depends on your environment really and your set standards. There is no one disadvantage or advantage over a named instance vs a default instance that I know of. The only thing I can think of is you can of course only have one default instance on the one server
[sub]____________ signature below ______________
The worst mistake you'll ever make is to do something simply the way you know how while ignoring the way it should be done[/sub]
We use named instances becuase it keeps applications seperate. For example we have one for financial. one for call management, one for EDI, etc. If you only have one instance anyway, I can't think of a real advantage.
Suppose you purchase software from a company that uses a SQL database. Also suppose that this software requires system administrator priveleges. Obviously, this wouldn't be the best way to write the software, but just suppose it existed.
Now, you wouldn't necessarily want this software to have access to other data that you may be storing in your system, so, you could create a named instance and give them system administrator priveleges to that instance.
-George
Strong and bitter words indicate a weak cause. - Fortune cookie wisdom
>>What are the advantages or disadvantages to using named instances over a default instance?
You can have multiple named instances but only one default. sometimes when you instal different versions you have to make one of them a default instance
And Like George said security, however I don't run multiple instances except on staging/development boxes
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.