We have a number of SQL Server 2008 R2 standard servers, each for a single application that we'd like to consolidate into one physical server. Running perfmon on these servers they're not using a high amount of CPU, IO, or network traffic so they're good candidates for consolidation. A couple of questions:
Is it better to create a single instance with multiple databases, or multiple instances (e.g. an instance for each application?)
I don't anticipate much contention, but is there a way to do some sort of governance on IO so that no database/instance can take up all the IO resources? I know I can do CPU with the resource governor.
On RAID configuration, we'll have 22 disks available (and 2 hot spares). Writes are heavier than reads so we'll do RAID-10.. Is it better to setup one large array for all the databases, and then two smaller arrays for log files and tempdbs, or setup a dedicated array for each database/instance.