Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 General SQL Server Forums
 New to SQL Server Administration
 When and How to create a New SQL Server Instance ?

Author  Topic 

saaas2015
Starting Member

1 Post

Posted - 2014-09-14 : 08:12:17
Hi,

I am new to SQL Server Admin. and I would like to know under what circumstances we should create a New SQL Server Instance.

What are the Pros and Crons of creating a New Instance when one instance is already running on the server.

How can we avoid creating a New Instance and the same job can be done with the help of creating a New Database ?

Thanks
Saleem

Shanky
Yak Posting Veteran

84 Posts

Posted - 2014-09-16 : 06:45:29
Question is quite open and too broad.

Hope this helps

Regards
Shanky
http://social.technet.microsoft.com/wiki/contents/articles/24253.list-of-articles-by-shanky.aspx
Go to Top of Page

Bustaz Kool
Master Smack Fu Yak Hacker

1834 Posts

Posted - 2014-09-16 : 12:28:24
Personal opinion: I dislike using multiple instances on the same server. My main objection is resource management. On the one hand, I don't want one instance hogging a particular resource, memory for instance, so I should place a limit on how much it can have. On the other hand, if one instance is doing some processing and the other instances are idle, I want all unused resources to be available. I have never heard a convincing argument in favor of multiple instances. The argument I hear most often is that there is greater security since different instances could have a different set of Logins I don't quite buy into this. If database X is placed in the same or a different instance, I still need to map Logins to Users and assign rights appropriately. With the "Contained" databases available in later editions of SQL, any security gain from the instance is even less relevant.

Just an opinion but at least its mine....



Too often we enjoy the comfort of opinion without the discomfort of thought. - John F. Kennedy
Go to Top of Page

jackv
Master Smack Fu Yak Hacker

2179 Posts

Posted - 2014-09-17 : 01:51:26
A key decision to make , if you were to go the multiple instances route is that full database worker isolation is not possible as they are operating on a shared OS , utilising a shared IO subsystem.
There are a number of other factors , such as overall licensing (including non SQL Server licenses for supporting agents etc), management overhead,etc. There are a load of other factors , some are listed here:
http://www.sqlserver-dba.com/2011/03/database-server-consolidation.html

Jack Vamvas
--------------------
http://www.sqlserver-dba.com
Go to Top of Page

jcgomez16
Starting Member

2 Posts

Posted - 2014-09-22 : 12:51:33
Hello,

If you are going to manage many database that, for the third party software it´s required to have an explícit database name, you can install multiple instance, but, in my personal experience, difficult more the phisycal resource configurations and administration.

Hope this help.
Go to Top of Page
   

- Advertisement -