One Cluster to rule them all

  • Hi

    We're looking to consolidate our many SQL server instances into 1 or more large SQL 2017 clusters running on VmWare.

    It's been suggested that all our production databases could be migrated to a single cluster. What are the reasons you might want multiple clusters? The only things I could think of were collation differences, potential backup issues and maybe CPU contention for parallelism. Is there a best practice or guidelines?

    We also need to size CPU usage, is there a best practice way of doing this? 

    Cheers

    Alex

  • Hi,
    you need to know what kind of application you use
    - OLTP
    - OLAP
    I  think it would not the best solution, to put them together on one cluster, ore?
    Are all applications able to use the same sql server version?
    What about sql server features like
    - SSRS
    - SSAS
    Both are not able to run on a sql server cluster

    Kind regards,
    Andreas

  • alex.palmer - Friday, November 3, 2017 8:53 AM

    What are the reasons you might want multiple clusters?

    Separation of nodes using completely disparate hardware

    alex.palmer - Friday, November 3, 2017 8:53 AMThe only things I could think of were collation differences

    Separate clustered instances, not separate clusters though

    alex.palmer - Friday, November 3, 2017 8:53 AMpotential backup issues 

    Doesnt warrant a separate cluster, what issues specifically?

    -----------------------------------------------------------------------------------------------------------

    "Ya can't make an omelette without breaking just a few eggs" 😉

  • alex.palmer - Friday, November 3, 2017 8:53 AM

    Hi

    We're looking to consolidate our many SQL server instances into 1 or more large SQL 2017 clusters running on VmWare.

    It's been suggested that all our production databases could be migrated to a single cluster. What are the reasons you might want multiple clusters? The only things I could think of were collation differences, potential backup issues and maybe CPU contention for parallelism. Is there a best practice or guidelines?

    We also need to size CPU usage, is there a best practice way of doing this? 

    Cheers

    Alex

    You might want to put separation of duties into that list as well.  Sometimes it is a requirement to keep business activities separated from one another even at the instance level.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply