Re: Running multiple instances in production environment. Good or bad?
From: Per Williamson (per.williamson_at_bredband.net)
Date: 02/02/05
- Next message: Wayne Snyder: "Re: Recommended # of columns per table?"
- Previous message: Wayne Snyder: "Re: Upsizing creates huge MSSQL"
- In reply to: Mike Epprecht (SQL MVP): "RE: Running multiple instances in production environment. Good or bad?"
- Next in thread: Wayne Snyder: "Re: Running multiple instances in production environment. Good or bad?"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 2 Feb 2005 14:42:38 +0100
Thanks Mike!
Per Williamson
Stockholm, Sweden
"Mike Epprecht (SQL MVP)" <mike@epprecht.net> skrev i meddelandet
news:6A40E1C4-6023-4EF5-95E5-DECC0A100F14@microsoft.com...
> Hi
>
> We run multiple instances on single servers (or clusters). We are a very
> large Financial Institution, with a trading floor. Server consolidation
> has
> become a big requirement.
>
> As long as you don't put more than 1 heavily used instance with another
> one,
> you are fine. It is best to limit each instances memory so that one does
> not
> dominate another one (Max Server Memory setting). If you have 2Gb, and
> both
> instances' use are equal, limit each one to 900Mb each (and leave the rest
> for the OS). If you want to, you could even limit each instance to only
> one
> processor (processor affinity).
>
> Make sure that your disks are optimized, at least (RAID-10 or RAID-1) for
> the transaction logs.
>
> We are happy with the path we went.
>
> Regards
> Mike
> "Per Williamson" wrote:
>
>> Hi there,
>>
>> Hoping to get a answers from people with "real life" experience of
>> running multiple Sql server instances!
>>
>> I have two different application using two different sets of
>> application databases, and for licensing reasons I´m going to let them
>> use the same physical database server. Both of them, I should mention,
>> require fairly low performance (5-10 concurrent users, resp. 1-2
>> concurrent users). My server has two 2.6 Ghz processors and 2 Gb
>> memory.
>>
>> As I have a Sql Server Standard Edition, "Per Processor" license, I am
>> now considering to have two different Sql Server instances, serving
>> one application each. Some of advantages, as I see them are:
>>
>> 1) The "owners" of the different applications feel they have their
>> "own" server (may be of psychological importance)
>> 2) Separates the SA roles, and improves security.
>> 3) One of the application is new to the organization and will need a
>> "running-in" period. Makes it possible to avoid disturbance in case of
>> needing to restart Sql Server.
>>
>> I have read some of the postings in this forum, and most of them seem
>> to be negative to running multiple instances in a production
>> environment, mainly due to the fact they will compete for system
>> resources.
>>
>> I now wonder if there are people out there with real experience of
>> running multiple instances. In theory, performance can suffer hard,
>> but in practice? Is it stable?
>>
>> Thanks in advance
>>
>> Per Williamson
>>
- Next message: Wayne Snyder: "Re: Recommended # of columns per table?"
- Previous message: Wayne Snyder: "Re: Upsizing creates huge MSSQL"
- In reply to: Mike Epprecht (SQL MVP): "RE: Running multiple instances in production environment. Good or bad?"
- Next in thread: Wayne Snyder: "Re: Running multiple instances in production environment. Good or bad?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
