Hi,
I have a big doubt about...

We have near 20 dbs with many applications that work with.

During the days there are many problems about coesistence, because
some applications are very CPU and disk expensive.
nevertheless the are some applications that require failover architecture so
we use clustering (MS).

So...

The only way I know to preserve cpu usage is to use multi-istance ( I mean
ServerA\sql01, ServerA\SQL02 )
and configure in the SQL properties the CPU to use.

Now.... the problem is :

- If I need to preserve CPU usage and I need failover ... do I have to put
a DB on separate cluster group ?

If so, the problem become the disks, because different cluster group cannot
share the same disks so
If I want to separate logs, data, index, temps... and so on I need tons of
physical disks...

Please, does anyone have some opinions ?


Thanks....

You may want to look into a Windows 2003 cluster. You can easily setup a 3
node cluster with 2 active and 1 failover. Then split the "intense"
application betwen the 2 Active nodes. If needed install additional SQL
instances for low-volumne applications.

You can set the Affinity Mask to control which SQL Server instance gets
which CPUs. For example, if you have 4-CPU nodes had 2 high volume
application, run each high volumne in their own instance with 3 CPUs each.
Then give the last CPU to the other instance on that node for low volumne
database applications.

Chris Skorlinski
Microsoft SQL Server Support
Please reply directly to the thread with any updates.

This posting is provided "as is" with no warranties and confers no rights.