none
SQL Clustering for System Center 2012

    Question

  • Hi,

    We are planning to implement System Center 2012 SP1 (SCCM, SCOM, SCVMM) on Windows Server 2012 with two node cluster SQL server 2012 to host database for all the mentioned products to achieve high availability.

    There are -

    • 3 sites of SCCM 2012 so there will be 3 databases.
    • 1 SCOM 2012 server so it will have 3 databases (OpsMgmr, OpsDW, Reportserver)
    • 1 SCVMM 2012 server so it will have 1 database.

    Like this there will be total 7 databases in SQL 2012 cluster.

    So want to understand,

    1. Is this recommended to do such configuration?
    2. What is the best recommended configuration to host SQL database for all the above products in cluster?
    3. Whether to install SQL database with default instances or named instance for each application?
    4. As reporting service is not cluster aware then how to install reporting server for all the mentioned products in cluster or way out for this?
    5. Are there any issues or challenges if we go with named instance for each application?

    Please guide.

    Sunday, August 25, 2013 9:51 AM

Answers

    1. Is this recommended to do such configuration? 

    You can go with your requirement, its not so complex design.

    2. What is the best recommended configuration to host SQL database for all the above products in cluster?

    For cluster support for application you need to go through with application details. Normally, most of the application works fine as application works on SQL VIP & remain  unaware that sql is standalone or cluster.

    3. Whether to install SQL database with default instances or named instance for each application?

    SQL Server works fine for both default & instance. It will not impact application &  its performance.

    4. As reporting service is not cluster aware then how to install reporting server for all the mentioned products in cluster or way out for this?

    You need to install reporting services on both node separably & configure them on both node separably.

    Help Link : http://technet.microsoft.com/en-us/library/bb630402.aspx

    5. Are there any issues or challenges if we go with named instance for each application?

    No.


    Regards,
    Rohit Garg
    (My Blog)
    This posting is provided with no warranties and confers no rights.
    Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread.

    Sunday, August 25, 2013 2:07 PM
  • 4. Please elaborate meaning of Failover clustering is supported only for the report server database; you cannot run the Report Server service as part of a failover cluster.” This is the statement from http://technet.microsoft.com/en-us/library/bb630402.aspx link.

    As per my understanding we installed the reporting server database on the server running reporting service. Please correct if I am wrong.

    Hello,

    SQL Server Reporting Services itself is not Microsoft cluster aware, meaning you cannot install it as a cluster resource. Failover Clustering with SSRS is possible, though there are a number of considerations and manual steps involved.

    As for ReportServer databse, you can use local or remote instance to host the databse. For example, you can create a cluster for the SQL Server instance, and then create the reporting services database on that instance while the Reporting Services install on a difference instance at separately server.

    If you have a requirement on the availability of Reporting Services functionality, the best way is use the Scale-out deployment which provides a way for multiple report servers to share the same catalog database.

    Reference:
    High Availability – Frequently Asked Questions about Failover Clustering and Reporting Services
    Planning a Deployment Topology

    Regards,
    Fanny Liu


    Fanny Liu
    TechNet Community Support

    Monday, August 26, 2013 2:50 AM

All replies

    1. Is this recommended to do such configuration? 

    You can go with your requirement, its not so complex design.

    2. What is the best recommended configuration to host SQL database for all the above products in cluster?

    For cluster support for application you need to go through with application details. Normally, most of the application works fine as application works on SQL VIP & remain  unaware that sql is standalone or cluster.

    3. Whether to install SQL database with default instances or named instance for each application?

    SQL Server works fine for both default & instance. It will not impact application &  its performance.

    4. As reporting service is not cluster aware then how to install reporting server for all the mentioned products in cluster or way out for this?

    You need to install reporting services on both node separably & configure them on both node separably.

    Help Link : http://technet.microsoft.com/en-us/library/bb630402.aspx

    5. Are there any issues or challenges if we go with named instance for each application?

    No.


    Regards,
    Rohit Garg
    (My Blog)
    This posting is provided with no warranties and confers no rights.
    Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread.

    Sunday, August 25, 2013 2:07 PM
  • 3. I have not experienced but heard that there are some issues/challenges with named instances in SQL cluster but also read that MS recommends named instance in SQL cluster so can any one share their experience to choose between default instance and named instance, since we have to plan this cluster for 3 different applications of System Center 2012.

    4. Please elaborate meaning of Failover clustering is supported only for the report server database; you cannot run the Report Server service as part of a failover cluster.” This is the statement from http://technet.microsoft.com/en-us/library/bb630402.aspx link.

    As per my understanding we installed the reporting server database on the server running reporting service. Please correct if I am wrong.

    • Edited by Parag_M Sunday, August 25, 2013 5:57 PM
    Sunday, August 25, 2013 5:39 PM
  • 4. Please elaborate meaning of Failover clustering is supported only for the report server database; you cannot run the Report Server service as part of a failover cluster.” This is the statement from http://technet.microsoft.com/en-us/library/bb630402.aspx link.

    As per my understanding we installed the reporting server database on the server running reporting service. Please correct if I am wrong.

    Hello,

    SQL Server Reporting Services itself is not Microsoft cluster aware, meaning you cannot install it as a cluster resource. Failover Clustering with SSRS is possible, though there are a number of considerations and manual steps involved.

    As for ReportServer databse, you can use local or remote instance to host the databse. For example, you can create a cluster for the SQL Server instance, and then create the reporting services database on that instance while the Reporting Services install on a difference instance at separately server.

    If you have a requirement on the availability of Reporting Services functionality, the best way is use the Scale-out deployment which provides a way for multiple report servers to share the same catalog database.

    Reference:
    High Availability – Frequently Asked Questions about Failover Clustering and Reporting Services
    Planning a Deployment Topology

    Regards,
    Fanny Liu


    Fanny Liu
    TechNet Community Support

    Monday, August 26, 2013 2:50 AM
  • Thanks for reply...
    Monday, August 26, 2013 2:00 PM