|  Login
September 02, 2010  
 
Search
 

Steps I took to install SQL Server 2005 Express Edition

I just started a new project and the first thing I had to do was install SQL Server 2005 on my Windows XP professional development machine. Here’s what I did from start to finish.

Download the necessary files

At the time of writing, SQL Server 2005 is on Service Pack 1. To  get it, go to http://msdn.microsoft.com/vstudio/express/sql/download/ and get the SQL Server 2005 Express Edition and SQL Server Management Studio Express OR Microsoft SQL Server 2005 Express Edition with Advanced Services and Microsoft SQL Server 2005 Express Edition Toolkit SP1.

Install the Microsoft .Net framework 2.0

My first step was to install the .Net framework 2.0. I found it by doing a Google search on .Net framework 2.0. It was pretty easy to install, but I’ve been hesitant to do it since I have Visual Studio 2003 installed and I actively work on many projects using it. I was worried my whole machine would be hosed, but several people now have told me that everything coexists nicely so I went ahead with it.

Update Windows to the latest Service Pack

I went to windowsupdate.microsoft.com where I had to download and install a new version of the windows installer. Again, not too much to it. I ran the new windows update and it found an update, the Microsoft Genuine Advantage tool. Sorry, Microsoft, I have enough Spyware on my computer telling the world what I do already. I’m legit, I know it, and I can prove it if necessary but I don’t want a tool on my computer installed to tell me I’m on the straight and narrow. I can’t see how anyone would ever install this knowingly!

Anyway, I checked my current service pack in the Control Panel under System. I was indeed using Service Pack 1. I wonder why windowsupdate wouldn’t give me the service pack? I did another Google search and found that I could download the file at http://www.soft32.com/Download/Free/Windows_XP_Service_Pack_2/4-992-1.html

I’ve been warned to Backup my system and close all open programs. Two phrases that developers everywhere hate to hear. The first few minutes went pretty smoothly, then I got to a point where I was almost finished and setup told me it was cleaning up the installation. Three and a half hours later, setup was telling me that it was cleaning up the installation. I finally got tired of waiting so I restarted my computer. Wouldn’t you know that my installation finished at exactly the same time and wanted to reboot? Coincidence? Not likely.  As the screen went dark, I sat in anticipation of the blue screen of death immediately when the computer came back to life. I logged in, I messed around a bit. Everything seems fine.

Run the installation of SQL Server 2005 Express

Thinking that I was off the hook, I casually clicked on the installation executable I had downloaded sometime in February. I passed all the checks with only one warning (so my hardware is barely sufficient to support the database?) and I happily pressed Next, Ok, I agree, Default, and whatever else I was forced to respond. A gigantic, ugly error!

Microsoft SQL Server Native Client -- Error 1706. An installation package for the product Microsoft SQL Server Native Client cannot be found. Try the installation again using a valid copy of the installation package 'sqlncli.msi'.

I clicked cancel, my installation rolled back and now I sit awestruck with my head in my hands.  Time for Google again. From Microsoft I found:

Setup might fail and roll back with the following error message: <aforementioned message /> To work around this problem, uninstall SQL Native Client by using Add or Remove Programs. On a cluster, uninstall SQL Native Client from all nodes. Then, run SQL Server Setup again.

Its actually called “Microsoft SQL Server Native Client.” Not that I’m keeping score or anything. After I uninstalled the offending program, the SQL Server 2005 Express edition installed successfully.