Sunday, September 28, 2008 10:13 AM
Brian S. Tucker
SCCM 2007 Using SQL 2008
In various places, recently I have been suggesting that you do not use SQL 2008 with SCCM 2007. The reasons that I say this is because a very knowledgeable resource at Microsoft stated that the code for SCCM 2007 was not written to work with SQL 2008. SQL 2008 has been completely redone and (from what I was told in person) is that "don't do it". Now, I have full respect for my friend Cliff Hobbs, but his post to his site suggests the following.
While though I was told that this was unsupported, I wonder if anyone has attempted to see if this will work (outside Microsoft). I think the way to do it is to try it out in a lab if you feel the need to go to SQL 2008. SCCM 2009 is almost ready to be available for TAP and unless you plan on being a TAP program organization, I would suggest sticking with SQL 2005. I was told that SCCM 2009 is designed to run under SQL 2008, so in my opinion, I would stick to what the code was written for. Updates are great and a workaround can be good, but unless you FULLY understand WHY you want to run SQL 2008, then why bother for now? On a side note, any organization running SQL 2005 should be testing SQL 2008. Remember, SQL is not only used by SCCM, but also for WSUS 3.0 SP1 for Software Updates. If you have the WSUS DB on the same SQL server if running 2008, then will WSUS work and what fixes will you need for that.
Simply put, think about what you need and don't jump the gun to a new version of SQL unless you fully understand all the issues that surround it. I don't think Cliff is suggesting you junp the gun either, he is giving updated information as we all do and I simply want to make you think about it before you find yourself in hot water.
Filed under: Systems Management, SCCM 2007, CM 2007, SCCM SP1, SQL 2008, SQL 2005