[We got a reader request for information about the versions of SQL Server supported by Configuration Manager 2007.
has provided the answer in today's post.]
As part of the planning considerations for Configuration Manager 2007 (ConfigMgr for short) deployment, we need to determine which version of SQL server will be used to host the site database. Before the release of SQL Server 2008 and later SQL Server 2005 SP3, the only SQL Server version supported to host the ConfigMgr site database was SQL Server 2005 SP2.
With the release of SQL Server 2008, the SQL support scenarios became a little complex. Hopefully, this post will clear things up and help you to figure out the right deployment or upgrade strategy.
Following is an overview of the Configuration Manager 2007 support for the different SQL Server versions:
SQL Server 2005:
ConfigMgr RTM and SP1 support SQL 2005 SP2 and SP3. Currently, no hotfix is required.
ConfigMgr R2 supports SQL 2005 SP2 and SP3, with hotfix
SQL Server 2008:
ConfigMgr RTM supports upgrading an existing SQL 2005 site database to SQL 2008, with hotfix
; but does not support new installation using a SQL 2008 instance to host the site database.
ConfigMgr SP1 supports SQL 2008, with hotfix
If you plan to use SQL Server 2005 for your site database implementation, the story is simple and easy. ConfigMgr RTM and SP1 can use SQL 2005 SP2 to host the site database with their original release - no hotfix is required. The only exception is ConfigMgr R2, where the client status reporting feature requires hotfix
to work with site database in a SQL named instance.
Now, let's talk about using SQL Server 2008 to host the ConfigMgr site database.
SQL 2008 was released in August 2008, several months after the release of ConfigMgr SP1. We started to test SQL 2008 Beta and RC (Release Candidate) while ConfigMgr SP1 was still under development. Several issues were identified and were fixed in SP1, including three issues in the site server setup program.
So, the ConfigMgr SP1 setup program works correctly with a SQL 2008 site database; but the ConfigMgr RTM setup program does not. That's why ConfigMgr RTM does not support fresh install using a SQL 2008 site database.
In order to get ConfigMgr RTM to work with SQL 2008, you will need to have an existing ConfigMgr RTM site with a SQL 2005 site database. You install hotfix
and upgrade SQL 2005 to SQL 2008. You can choose to install the hotfix either before or after you upgrade SQL. This single hotfix addresses a status summarizer issue, a distribution manager issue, and an admin console OSD driver management node issue.
The OSD driver management node issue was discovered after SP1 was released. So if your ConfigMgr SP1 site uses SQL 2008 to host the site database, you need the hotfix
to address the OSD driver management node issue. This applies for both a fresh SQL 2008 installation or one upgraded from SQL 2005, when used to host the ConfigMgr SP1 site database.
Finally, we had the ConfigMgr R2 release which brought us the lovely SQL reporting services (SRS) and a client status reporting tool, among other great features. The hotfix
addresses a SQL reporting services problem where you see error messages about SRS in system status. This error does not affect the functionality of reports, although it generates false notifications.
Update to original post:
Installing the hotfix
error ID 7404
appearing in status messages. If you see
error ID 7403
in status messages, but you are not experiencing any problems with SQL Reporting Services in Configuration Manager, install the
Cumulative Update 4 for SQL Server 2008 R2
If your site database resides in a SQL named instance, the client status reporting feature requires hotfix
. This is true for both SQL 2005 and SQL 2008.
Please note that this blog post is not the official support statement. You may find the official support statement