Previous to today, using SQL 2008R2 as a back end database instance for the Operations DB, Warehouse DB, or SSRS reporting instances was not supported.
Over on the MOMTEAM BLOG and in KB2425714, they just published a support statement for SQL 2008R2.
This is being handled in two phases:
Phase 1: New installations of OpsMgr 2007 R2. This is supported as of this writing, using special steps outlined in http://support.microsoft.com/kb/2425714 Note, there are some special steps to get this working, and there are some known issues with no workarounds if you must use 2008R2 at this time.
Phase 2: Upgrading an existing installed management group from (SQL 2005SP3 or SQL 2008SP1) to SQL 2008R2. This is NOT supported/available yet. This is the process to upgrade your existing management group database and reporting instance roles to SQL 2008R2. This is planned for a future CU (cumulative update) which will add support for this process.
*** NOTE for ACS: While the KB above does not mention it – ACS is also supported for NEW installations of the ACS DB and reporting website, on SQL 2008 R2. UPGRADE of an existing ACS environment to SQL 2008R2 is not yet supported, consistent with the OpsDB, Warehouse, and reporting roles.
Any news on support for the ACS database?
Good catch - I updated the article.
ACS is supported for NEW DB's - not upgrades, just like the other roles.
There are a couple of posts in the General forum of technet forums that are from people having problems with a remote (from the Data Warehouse) SQL2008 R2 Reporting Server. Do you know if this has been tested? Or supported?
I havent seen or played with that yet. I advise my customers to wait for full support in the upcoming CU that will add support for SQL 2008R2 (and likely SQL 2008 SP2)
Damn, I just saw this post now. We have already moved Operational DB, Datawarehouse DB, and ACS DB to SQL 2008 R2 - Do any of you have any ideas what could happent??? or what is not working in our setup?
Here is a littel more info - we Made compleate new SQL clusters installed with SQL 2008 R2 and then we moved the database from the old server installed with SQL 2005 SP3.
Should we move all the databases back to the SQL 2005 SP3 server, and then reinstall the new server with SQL 2008 SP1 and then move them back to the new servers again.
Or shuld we just leave them running on the SQL 2008 R2 and wait for the update to support SQL 2008 R2 ??
To be in a supported configuration, I'd say yes.
However, if you were able to move them, and you dont see anything broken....
Did you leave your SRS/Reporting server alone and only move the OpsDB and DW databases?
We have been running on the SQL 2008 R2 for around 2 month now (OpsDB, DW-db and ACS-db) without any problems... so I think I will keep it like this. We are still running the reporting server on SQL 2005 reporting, but we have plans to upgrade it to SQL 2008 R2 (the ACS reporting servers are running on SQL 2008 R2 without any problems) - do you have any recommendations on what we should do about the reporting server when we want to upgrade it?
Running mixed version of SQL between the OpsDB and Reporting is unsupported. Of course - that doesnt really matter to you at this point - as your entire environment is unsupported due to the fact you upgraded.
Irregardless, I would recommend doing nothing if it is working now. Historically the reporting server is where we have had the most issues with new versions of SQL. I would recommend waiting until CU4, and when we announce support for SQL 2008 R2 for all roles and upgrade scenarios, and then consider the upgrade of reporting.
Okay - thank you a lot for the input, it help me a lot - so now I can sleep better :o)
Any Idea when the CU will be released? I really need to move my db's and dont really want to use 2008 when support for 2008 R2 is coming.
No idea.... however, in the past these have been somewhat quarterly-ish once they started.
R2 RTM - May 2009
R2 CU1 - Jan 2010
R2 CU2 - April 2010
R2 CU3 - Oct 2010
Any idea on when the OpsDB and OpsDW installation using the DBCreateWizard on SQL 2008R2 will support an automated command line installation?
@Tom - no idea. Not even sure if that is planned.
Cusrious - why is a command line automated solution required to deploy a database component? I would expect most large companies I work with deploy the database components once for the life of the product. If you require this I would open a case on that and get it filed as a DCR with a business justification.
CU4 for SQL 2008 R2 came out on 10/18....