SQL 2005 servers with multiple instances
- From: "Chris Williamson" <cwilliamson13@xxxxxxxxxxxxxxxxx>
- Date: Wed, 15 Mar 2006 23:59:57 -0600
I have an interesting configuration that I was hoping others might comment
on. We have 2 SQL 2005 standard servers that need to provide redundancy for
each other, without using clustering. We'll be replicating the databases
from one server to the other, and vice-versa.
Our big question is, should we use multiple instances? The knee-jerk
reaction is to not use instances because of the extra overhead and the
inefficient sharing of memory between the instances. However, I have a few
reasons why it would be beneficial...
First, consider the two servers with many small drives for the 'Live' data
(4 logs, 7 data all 15k), but a small number of large drives for the
'Redundant' data (4 for Data and logs, only 10k). The same RAID controller
is being shared for the Live data and the Redundant data/logs. Also, we're
using processor licensing, so the additional instances won't cost any more.
My concern is the load affecting the Live databases while applying
transaction logs to the Redundant databases, which would be done at least
every 30 minutes. To my knowledge, SQL provides no prioritization, other
than setting proc affinity and boosting priority.
I'm proposing that we use two instances on each server - Live and Redundant.
Server1\Live would replicate to Server2\Redundant, and Server2\Live would
replicated to Server1\Redundant. The Backup instances would be limited to
256MB memory and have its cpu & io affinity set to one of the dual
hyperthreaded processors. This would ensure the Live instance always takes
precedence over the backup instance. Even if everything is at 100%,
theoretically, Live would have 87% of the resources (3 processors + 1/2 of
the fourth). The backup instance wouldn't be doing anything except
restoring logs, so there shouldn't be much loss due to overhead.
Obviously, during a (manual) failover, the memory and affinity would be
adjusted. Not as fancy Clustering, but doesn't have the price tag either.
I totally understand the extra overhead if dealing with two instances that
are very active. But in this situation, I don't think there'd be a problem.
Does anyone have any comments or helpful hints with our configuration?
Thank you,
Chris
.
- Follow-Ups:
- Re: SQL 2005 servers with multiple instances
- From: Geoff N. Hiten
- Re: SQL 2005 servers with multiple instances
- Prev by Date: Re: Need Help regarding SQL Server 2005
- Next by Date: Re: SQL Server 2005 Installation
- Previous by thread: Re: SQL Server 2005 Installation
- Next by thread: Re: SQL 2005 servers with multiple instances
- Index(es):
Relevant Pages
|
Loading