Are you familiar with the proverb: "When everything is normal, there is always something wrong". That's true, and that's what happened to me. I installed at least more than 10 times visual Studio. NET (vs.net) and SQL Server 2005 under the development platform of multiple machines.
I recently replaced a hard drive, reinstalled Windows XP systems, and partition Magic, NoteTab, and other useful tools, and finally installed Office 2003, vs.net, SQL Server 2005, and MSDN. Then I clicked on the "Start-〉 Program" menu, and to my surprise, Management Studio, Analysis Services, and Business Intelligence Studio in SQL Server 2005 were gone.
At the same time, I went to a training school to teach SQL Server courses. This course has been taught in MySQL, but now I'd like to use SQL Server 2005, and I suggest that the school technician download the SQL Server version of Express (this version is free and there will be no copyright disputes). When I got there the first day, I found that the technicians had done my job well and all the software was installed. But I still had a problem, and it was a big problem: the same problems I had at home.
I call a lot of friends and colleagues I respect. Stephen Giles, a good friend of mine, has confirmed his suspicions. The problem arises because of the existence of SQL Server Express.
At home, I first installed the vs.net and then installed SQL Server 2005. During the installation of Vs.net, a check box appears, prompting you to install SQL Server Express. At the Training institute, the technicians were there to follow my instructions and install SQL Server Express.
After that, if you try to install SQL Server 2005, the installer notifies you that the system is installed with SQL Server Express, and that you should skip the installation of many wonderful GUI tools (because SQL Server 2005 These GUI tools are not included in Express.
In my opinion, the installation process for SQL Server 2005 is not perfect; it should at least set the SQL Server 2005 installation checkbox by default to "false" instead of "true." When the system has been detected with SQL Server Express, the installer should provide users with the following three choices:
1. Delete SQL Server's Express, install SQL Server 2005
2. Install SQL Server 2005 at the same time
3. Install SQL Server 2005 in the usual way
If you've ever had a situation like this (I hope it's not a problem at a particularly critical juncture). The following methods can help you solve the problem:
1. Remove all SQL Server 2005-related programs in the Control Panel.
2. If you have a registry collation tool, run it. This is not important, but I do this when I have a problem with the installation process.
3. Reboot.
4. Install the official version of SQL Server 2005.
Follow the above method to solve the problem, so that your program can work again.