I had the same problem. It can be avoided entirely if you install SQL Server 2005 before VS 2008, but if you are reading this then it is too late...