locked
Sql server 2008 instance along with SQL server 2005 Clustered RRS feed

  • Question

  • Is it possible to install and run SQL Server 2008 instance in the Windows 2003 Server which is already installed with SQL Server 2005 (Clustered)?

     

    Thursday, April 1, 2010 8:07 AM

Answers

  • For a clustered or for non-clustered environment?

    Clustered: This depends on the number of nodes that are in the environment, but the rule of thumb is only 1 instance per node with nodes available to take the workload should something arise. For example if you have a 2-node cluster it's advised that only 1 instance be installed, however if you had a 6 node cluster it's up to you to decide how many instances can be stacked assuming failover and what partners those should be.

    Non-clustered: This is more hardware based and depends on the current environment. I would go any more than a few per server, especially since if it DOES go down, it's down. again though this will be based on your requirements - some of our servers have one instance with a great number of smaller databases that don't require the caveats of having their own instance (such as different service packs, different administrators, security requirements, etc).

    Hope this helps,
    Sean

    Thursday, April 8, 2010 9:54 AM
    Answerer

All replies

  • Hello,

    This should be possible, however adding anything extra that ins't inherent to the cluster is not recommended, nor is overloading the cluster with extra instances.

    Hope this helps,
    Sean

    • Proposed as answer by William Vaughn Thursday, April 1, 2010 6:56 PM
    Thursday, April 1, 2010 6:55 PM
    Answerer
  • Thanks for your Reply Sean!!

    Could you guide me on how many number of instances is recommended to have in an pretty decent hardware configuration?

     

    Thursday, April 8, 2010 7:58 AM
  • For a clustered or for non-clustered environment?

    Clustered: This depends on the number of nodes that are in the environment, but the rule of thumb is only 1 instance per node with nodes available to take the workload should something arise. For example if you have a 2-node cluster it's advised that only 1 instance be installed, however if you had a 6 node cluster it's up to you to decide how many instances can be stacked assuming failover and what partners those should be.

    Non-clustered: This is more hardware based and depends on the current environment. I would go any more than a few per server, especially since if it DOES go down, it's down. again though this will be based on your requirements - some of our servers have one instance with a great number of smaller databases that don't require the caveats of having their own instance (such as different service packs, different administrators, security requirements, etc).

    Hope this helps,
    Sean

    Thursday, April 8, 2010 9:54 AM
    Answerer
  • For a clustered or for non-clustered environment?

    Clustered: This depends on the number of nodes that are in the environment, but the rule of thumb is only 1 instance per node with nodes available to take the workload should something arise. For example if you have a 2-node cluster it's advised that only 1 instance be installed, however if you had a 6 node cluster it's up to you to decide how many instances can be stacked assuming failover and what partners those should be.

    Non-clustered: This is more hardware based and depends on the current environment. I would go any more than a few per server, especially since if it DOES go down, it's down. again though this will be based on your requirements - some of our servers have one instance with a great number of smaller databases that don't require the caveats of having their own instance (such as different service packs, different administrators, security requirements, etc).

    Hope this helps,
    Sean

    Thursday, April 8, 2010 9:54 AM
    Answerer