Microsoft Product, Meet Microsoft Product

I was attempting to do a little programming exercise in C# yesterday when I discovered a configuration error on my computer. The exercise in question involved linking a SQL database to a Windows form, and whenever I tried to build the link I got an error. A bit of web searching revealed that the error seemed to stem from the two products— Visual Studio and SQL Server— not talking to each other.

Now, a few months ago I had installed some Visual Studio Express products as well as SQL Server Express. A week or so ago I installed Visual Studio Professional, and I figured that the link didn't get updated to the newer programming environment. So, last night, about Midnight, I started fixing the problem:

1. Step one was to remove all SQL Server products and VS Express products so that SQL Server could be reinstalled with the correct linking. Microsoft products always take far longer to install, reinstall, or repair so I was well delayed before finishing this step.

2. With the products removed, I popped the VS Professional DVD back in and ran a repair, figuring that SQL Server would be reinstalled correctly during the repair. The repair ran at least half an hour, and at the end I had no SQL Server at all. It seems it's not installed as part of VS Pro.

3. I hit Microsoft's website to download the installation software for SQL Server Express. This file was half a gig in size, which was not a problem, but it delayed me another 20 minutes while downloading.

4. Once downloaded, I cranked up the installation, which took me through several steps over a few minutes and finally got to a page of tests to see if my computer was adequate for the software. Like I said, this test, for some reason, comes a few minutes into the install— and my computer failed because it was missing a product called PowerShell, which is a scripting utility provided by Microsoft.

5. So, I cancelled out the install and hit the web to get PowerShell. PowerShell is available for free on Microsoft's website, but is only downloadable by those whose computers pass the 'Genuine Microsoft' authenticity test. Not a problem for me. My computer is 100% legitimate, and I've run this authenticity software before. I clicked the download button and ran the software only to get a return message saying that the software was out-of-date.

6. Hmmm. How to get around this block? It was about 1:30 AM by this time, and I was getting tired. The only thing I could think to do was to re-download the authenticator and try again. Fortunately, it worked the second time and returned a good authentication code, which I plugged back into the website, unlocking the ability to download PowerShell.

7. PowerShell installed in very little time.

8. I re-launched the SQL Server installation and made it past the page of tests with flying colors this time. Then, however, I got to several pages of configuration decisions. I had to stop and read each page and try to pick the best course of action, not knowing how these decisions will affect future uses of the the SQL Server software. (I'm still hoping I guess right.) After a few more minutes, I made it through the configuration and ran into a second page of computer tests... and, you guessed it, my computer failed one of the tests again. This time, it said that my version of VS Pro was older than the version of SQL Server I was attempting to install and, therefore, incompatible.  *sigh*

9. Now, I installed VS Pro with service pack 1, but, for some reason, the other software didn't think so. All I could think to do was hit Microsoft's website and run the SP1 update patch. This time, however, I did not cancel the current SQL Server installation. I didn't want to have to go through the configuration choices again. SP1 for VS Pro was easy to find and easy to launch, but, like a full installation, it took a long time to run. I didn't finish until about 2:30 AM.

10. With the SP1 update done, I clicked the button in the SQL Server installation to run the tests again, and all were passed just fine this time. SQL Server finally finished installing about 3 AM.

11. Just to be sure— since I had changed so much software on my system— I went to Microsoft's update website. Wouldn't you know, a SP1 update for SQL Server was found. I will let my clever readers find the irony in that! Regardless, this update finished just before 3:30 AM.

12. I restarted VS Pro to see if my data linking would now work, and it did! Hooray!! Only 3½ hours! Think about that the next time an I.T. guys says he needs your computer for a few hours or he wants to charge you $50 or $75 to look at your computer.   :-P

"The suddenness of the leap from hardware to software cannot but produce a period of anarchy and collapse, especially in the developed countries."— Marshall McLuhan