Installing SQL Server 2005 Tools AFTER Visual Studio Orcas
NOTE: I’m not sure if this is an Orcas issue, a SQL Server issue, or just the joys of an installation’s mislead logic…
Now that my system is primed with Orcas as the primary development platform, I finished up by installing SQL Server 2005’s management console (OT /whine: I still miss Enterprise Manager a bit).
*BOOM* Error: Edition Change Check. Ehh? I’ve gotten this on Vista before, but never on XP Pro SP2.
Oddly enough, the same steps fixed the problem:
- Go into Control Panel > Add/Remove Programs.
- Find “Microsoft SQL Server 2005” and click ‘Change’.
- Select the radio button for the Client Tools ONLY—unless you want to get rid of SQL Express as well.
- Check both and remove the Workstation Components, etc.
- Rerun your SQL Server 2005 installation.
You’ll still get the Edition Change Check error; however, instead of failing that there’s ‘nothing to do’, the installation will proceed normally and the workstaiton tools will install.
Note to Microsoft: The Edition Change Check is cool to help reduce mixed versions; however, there’s got to be a way to flag it that “HEY! I’m Visual Studio’s Express Edition—I’m not upgrading, I just want the tools to manage the other SQL Servers!”