Move Reporting Server to new computer RRS feed

  • Question

  • We have reporting services running in SCOM 2012 R2 on SQL 2008 R2. The DW and Ops DB are running on a SQL Cluster and SQL Reporting on a separate SQL 2008 R2 box. We wan't to move and upgrade reporting to a new SQL 2014 box. Have anybody done this? What is the procedure to use?




    Tuesday, January 19, 2016 9:14 AM


  • Hi There,

    There is a saying that the same version of SQL server version should be used for all the operationsmanager features by MS.

    So if you use SQL 2014, Then recommend to use SQL 2014 for the DB instances as well.

    Look at the second point.

    Also Clustered reporting is not supported by SCOM.


    SQL Server

    Check for updates and hotfixes for Microsoft SQL Server. See SQL Server in System Center 2012 R2.

    • Operations Manager does not support hosting its databases or SQL Server Reporting Services on a 32-bit edition of SQL Server.

    • Using a different version of SQL Server for different Operations Manager features is not supported. The same version should be used for all features.

    • For SQL Server collation settings, see SQL Server in System Center 2012 R2

    • The SQL Server Agent service must be started, and the startup type must be set to automatic.

    • The db_owner role for the operational database must be a domain account. If you set the SQL Server Authentication to Mixed mode, and then try to add a local SQL Server login on the operational database, the Data Access service will not be able to start. For information about how to resolve the issue, see System Center Data Access Service Start Up Failure Due to SQL Configuration Change

    • If you plan to use the Network Monitoring features of System Center 2012 R2 Operations Manager, you should move the tempdb database to a separate disk that has multiple spindles. For more information, see tempdb Database.


    Tuesday, January 19, 2016 7:37 PM

All replies