June 14, 2002 at 10:44 am
Kinda a followup to my other questions..
Are IT managers deploying MSFT SQL Server using Named Instances? I don't see much traffic or many questions about it.
June 14, 2002 at 11:04 am
We havent used it much. When it first came out it was handy since we could do some testing on the server that was running SQL 7 in production, I think we still have that setup on our development server just in case we need SQL7.
Andy
June 14, 2002 at 12:20 pm
Haven't used it. Tested, but haven't found a good reason to do it. It's mainly for desktop installs (why it was developed). I tend to try to build things that are database specific, not server, so different servers aren't an issue.
Steve Jones
June 14, 2002 at 12:49 pm
We only use named instances in our clusters. The named instance is required for an active/active cluster (can only have one default instance, and it can run on either physical server... therefore the second instance of SQL Server has to be named).
K. Brian Kelley
http://www.sqlservercentral.com/columnists/bkelley/
K. Brian Kelley
@kbriankelley
June 25, 2002 at 3:30 pm
I've actually used it a lot, primarily in situations where there was a desire to consolidate hardware and segregate security environments. It's a solution you really need to keep an eye on, and you absolutely positively MUST understand the usage patterns or your database. It's also very useful when you get some application vendor that demains SA access to help "fix" your database. I highly endorse it, but it requires planning and pretty thorough ongoing monitoring
June 25, 2002 at 5:28 pm
Curious, why does it help with Vendors? I can understand separateing the security environments, and it might be useful for applications like Great Plains which have hardcoded database names.
Steve Jones
June 25, 2002 at 6:21 pm
With vendors, the goal of multi-instance is exactly that -- segregating security environments. I've hit more than one 3rd party app where the Vendor where the vendor wants SA access to "configure" their application. Rather then giving them access to other databases, I prefer creating a separate instance with a pretty restrictive security environment (OA procedures removed, xp_cmdshell removed, etc).
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply