April 27, 2016 at 2:18 pm
Hi,
I saw the following statements in a SQL DBA 2008 R2 and 2012 class text, and wondered why you cannot install all components in more that one instance? Does that mean you can’t have (or don’t want to have) more than one instance with the same component of SQL Server? Is it that you would have 1 database engine, and 1 copy of each component on a physical server, and then multiple instances of databases on it to utilize those components?
Quote from text starts here:
Additional instances of SQL Server require an instance name that you can use in conjunction with the servername and are known as named instances. If you want all your instances to be named instances, you do not need to install a default instance first. You cannot install all components of SQL Server in more than one instance. Toaccess a named instance, client applications use the address Server-Name\Instance-Name. For example, a namedinstance called Test on a Windows server called APPSERVER1 would be addressed as APPSERVER1\Test.
There is no need to install SQL Server tools and utilities more than once on a server. You can use a singleinstallation of the tools to manage and configure all instances.
Quote from text ends here:
April 27, 2016 at 4:08 pm
RickNPHX (4/27/2016)
Hi,I saw the following statements in a SQL DBA 2008 R2 and 2012 class text, and wondered why you cannot install all components in more that one instance? Does that mean you can’t have (or don’t want to have) more than one instance with the same component of SQL Server? Is it that you would have 1 database engine, and 1 copy of each component on a physical server, and then multiple instances of databases on it to utilize those components?
Quote from text starts here:
Additional instances of SQL Server require an instance name that you can use in conjunction with the servername and are known as named instances. If you want all your instances to be named instances, you do not need to install a default instance first. You cannot install all components of SQL Server in more than one instance. Toaccess a named instance, client applications use the address Server-Name\Instance-Name. For example, a namedinstance called Test on a Windows server called APPSERVER1 would be addressed as APPSERVER1\Test.
There is no need to install SQL Server tools and utilities more than once on a server. You can use a singleinstallation of the tools to manage and configure all instances.
Quote from text ends here:
I believe the text would be more accurate if it said this:
Even though a server may have multiple instances installed, that does not mean that all of the SQL Server components have been installed multiple times
Otherwise, the implication is that there is only one instance in the world which has all components installed 🙂
Instead, what happens is that some of the components get shared between the instances.
It does not mean that there are limited features available in some of the instances.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
April 28, 2016 at 2:36 am
It just means that on a given server, the DLL and EXE files that make up the behavior of SQL Server can, for the most part, be installed once, and then used between multiple instances on that server. You can have, for example, in-memory OLTP on two instances. Same goes with the other functionality.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply