I have a SQL 2005 cluster as the backend of my OCS 2007 environment. It is a
shared server. I recently found information that the OCS DB should be on its
own SQL server, or at least its own instance with dedicated spindles for the
data and log files.

The cluster its on now is shared so I guess I'll need to create a new
instance.
Not having a huge SQL clustering background I did a little googl'ing and i
found some messages saying that instances are not support in an
active/passive cluster.
Is this true?

Thanks in advance!!!

Active - Active is the old terminology and now adays it is Single Instance
or Multi Instance clusters. And yes what used to be Active - Active can
support multiple Instances. As a matter of fact you have 2 instances by
definition if it was Active - Active. They just weren't both running on the
same node unless you had a failover.

But I question the logic of creating a new instance just for this one app.
While it is true that you should separate high volume db files onto separate
spindles you should look at the metrics to determine if this is necessary or
not. Putting it into its own instance will usually decrease performance not
increase it since each instance has to have a certain amount of resources,
mainly memory. You would be best to determine why and if you need to do
anything before going to the extreme of adding another instance to your
cluster.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Tom_Slycke" <tom_slycke (AT) cox (DOT) net> wrote

Active - Active is the old terminology and now adays it is Single Instance
or Multi Instance clusters. And yes what used to be Active - Active can
support multiple Instances. As a matter of fact you have 2 instances by
definition if it was Active - Active. They just weren't both running on the
same node unless you had a failover.

But I question the logic of creating a new instance just for this one app.
While it is true that you should separate high volume db files onto separate
spindles you should look at the metrics to determine if this is necessary or
not. Putting it into its own instance will usually decrease performance not
increase it since each instance has to have a certain amount of resources,
mainly memory. You would be best to determine why and if you need to do
anything before going to the extreme of adding another instance to your
cluster.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Tom_Slycke" <tom_slycke (AT) cox (DOT) net> wrote

Active - Active is the old terminology and now adays it is Single Instance
or Multi Instance clusters. And yes what used to be Active - Active can
support multiple Instances. As a matter of fact you have 2 instances by
definition if it was Active - Active. They just weren't both running on the
same node unless you had a failover.

But I question the logic of creating a new instance just for this one app.
While it is true that you should separate high volume db files onto separate
spindles you should look at the metrics to determine if this is necessary or
not. Putting it into its own instance will usually decrease performance not
increase it since each instance has to have a certain amount of resources,
mainly memory. You would be best to determine why and if you need to do
anything before going to the extreme of adding another instance to your
cluster.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Tom_Slycke" <tom_slycke (AT) cox (DOT) net> wrote

Active - Active is the old terminology and now adays it is Single Instance
or Multi Instance clusters. And yes what used to be Active - Active can
support multiple Instances. As a matter of fact you have 2 instances by
definition if it was Active - Active. They just weren't both running on the
same node unless you had a failover.

But I question the logic of creating a new instance just for this one app.
While it is true that you should separate high volume db files onto separate
spindles you should look at the metrics to determine if this is necessary or
not. Putting it into its own instance will usually decrease performance not
increase it since each instance has to have a certain amount of resources,
mainly memory. You would be best to determine why and if you need to do
anything before going to the extreme of adding another instance to your
cluster.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Tom_Slycke" <tom_slycke (AT) cox (DOT) net> wrote

Active - Active is the old terminology and now adays it is Single Instance
or Multi Instance clusters. And yes what used to be Active - Active can
support multiple Instances. As a matter of fact you have 2 instances by
definition if it was Active - Active. They just weren't both running on the
same node unless you had a failover.

But I question the logic of creating a new instance just for this one app.
While it is true that you should separate high volume db files onto separate
spindles you should look at the metrics to determine if this is necessary or
not. Putting it into its own instance will usually decrease performance not
increase it since each instance has to have a certain amount of resources,
mainly memory. You would be best to determine why and if you need to do
anything before going to the extreme of adding another instance to your
cluster.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Tom_Slycke" <tom_slycke (AT) cox (DOT) net> wrote

Active - Active is the old terminology and now adays it is Single Instance
or Multi Instance clusters. And yes what used to be Active - Active can
support multiple Instances. As a matter of fact you have 2 instances by
definition if it was Active - Active. They just weren't both running on the
same node unless you had a failover.

But I question the logic of creating a new instance just for this one app.
While it is true that you should separate high volume db files onto separate
spindles you should look at the metrics to determine if this is necessary or
not. Putting it into its own instance will usually decrease performance not
increase it since each instance has to have a certain amount of resources,
mainly memory. You would be best to determine why and if you need to do
anything before going to the extreme of adding another instance to your
cluster.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Tom_Slycke" <tom_slycke (AT) cox (DOT) net> wrote

Active - Active is the old terminology and now adays it is Single Instance
or Multi Instance clusters. And yes what used to be Active - Active can
support multiple Instances. As a matter of fact you have 2 instances by
definition if it was Active - Active. They just weren't both running on the
same node unless you had a failover.

But I question the logic of creating a new instance just for this one app.
While it is true that you should separate high volume db files onto separate
spindles you should look at the metrics to determine if this is necessary or
not. Putting it into its own instance will usually decrease performance not
increase it since each instance has to have a certain amount of resources,
mainly memory. You would be best to determine why and if you need to do
anything before going to the extreme of adding another instance to your
cluster.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Tom_Slycke" <tom_slycke (AT) cox (DOT) net> wrote

Active - Active is the old terminology and now adays it is Single Instance
or Multi Instance clusters. And yes what used to be Active - Active can
support multiple Instances. As a matter of fact you have 2 instances by
definition if it was Active - Active. They just weren't both running on the
same node unless you had a failover.

But I question the logic of creating a new instance just for this one app.
While it is true that you should separate high volume db files onto separate
spindles you should look at the metrics to determine if this is necessary or
not. Putting it into its own instance will usually decrease performance not
increase it since each instance has to have a certain amount of resources,
mainly memory. You would be best to determine why and if you need to do
anything before going to the extreme of adding another instance to your
cluster.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Tom_Slycke" <tom_slycke (AT) cox (DOT) net> wrote

Active - Active is the old terminology and now adays it is Single Instance
or Multi Instance clusters. And yes what used to be Active - Active can
support multiple Instances. As a matter of fact you have 2 instances by
definition if it was Active - Active. They just weren't both running on the
same node unless you had a failover.

But I question the logic of creating a new instance just for this one app.
While it is true that you should separate high volume db files onto separate
spindles you should look at the metrics to determine if this is necessary or
not. Putting it into its own instance will usually decrease performance not
increase it since each instance has to have a certain amount of resources,
mainly memory. You would be best to determine why and if you need to do
anything before going to the extreme of adding another instance to your
cluster.

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors


"Tom_Slycke" <tom_slycke (AT) cox (DOT) net> wrote