Hardware recommendations for two node cluster -- sql server clustering

Michael MacGregor
10/19/2007 10:48:40 PM

I am looking at putting the specs together for a new SQL Server 2005
cluster, two nodes. It needs to be capable of supporting multiple customer
databases, around 20-30, average database size is 3GB but several will be in
the region of 10-20GB, capable of handling 10,000 transactions per minute
minimum.

I am actually mostly interested in what would be required in order to
provide a cluster array that can provide physically separate disk drives so
as to place different databases on different drives, accessed by different
controllers, i.e. such that there is no bottleneck or disk contention, or to
at least minimise such.

Any and all recommendations are welcome.

Michael MacGregor
Database Architect

Linchi Shea
10/21/2007 4:32:01 PM

10,000 transactions per minute translates into ~200 transaction/second.
Depending on the I/O ratios per transaction, that may or may not be very busy
on the I/O system. Without knowing how many I/Os a transaction may incur,
it's difficult to meaningfully size the disk subsystem.

I'm not sure separate the databases onto their own I/O paths is necessarily
a good idea. I'd rather try to isolate the logs first. After that, I'll
stripe across as many spindles as possible and have the data files share the
the striped set(s). This is much simpler to manage, and may provide enough
I/O capacity. The best way to find out to run some load tests to get some
numbers.

Linchi

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about sql server clustering

sql server clustering : Hardware recommendations for two node cluster