The title is not really appropriate. I should call this post “How to get on someone’s nerves”.
After a fresh install of Windows Vista and Visual Studio 2008 I went on microsoft.com and downloaded the Express version of SQL Server 2008 (200 MB).
Started the installer and got a message informing me that I need .NET Framework 3.5 SP1 installed. Ok, no problem – went on the download site and got a 2 MB installer. It downloaded another 39 MB and then it took more time to install than was needed for Visual Studio 2008 Team Suite, Full Install. And it required a restart; Visual Studio Installer did not.
After this I restarted SQL Server installation. Guess what? Another message saying that I need Windows Installer 4.5. Again, go to microsoft.com, download the installer, install the update – took less time than .netfx 3.5sp1 – and restart.
Finally I was able to start SQl Server installer. Guess what? After the first check I got another prerequisites failure: Windows Power Shell. Go to microsoft.com (again), search for PowerShell, go on the download page, verify that Windows is Genuine, download, install. Now I got no warning for SQL Installer – Yupii! (but not for long).
The setup program installed a few componenents and… another check… this time it couldn’t find Visual Studio 2008 SP1… Go to microsoft (for the fourth time), download an 800 MB iso image, mount it and start the installer. Did I tell you that .NET Framework 3.5SP1 took a lot of time to install? Well, SP1 for VS2008 took almost double.
After 4 hours from the initial tentative of installation I was able to successfully complete the setup…
(+1 rating, 1 votes)
And what did you expect? It`s ‘Micro$oft’ duh !
That’s why I love Ubuntu :P.
At least you could appreciate that it allows you to install the server on other partition than C:. On a pentium 4/windows XP SP3 it took about 2 hours – that’s too much, compared to SQL Server 2005. Creepy… this way, it will not become very popular.
oh ye it sucks… that’s why i install the 2005 edition :D
I’ve been through pretty much the same thing just now on Server 2008.
The installer for SQL Server 2008 is simply pathetic.
Microsoft should be embarrassed with the installation issues SQL Server Express 2008 has. Im addition to all the above, I got a the following error: “The INSTANCESHAREDWOWDIR command line value was not specified. This value must be specified when the INSTANCESHAREDDIR value is specified.” What the hell is that? After searching, I found this error only occurs if an install dir different from the default one (C:\Program Files\Microsoft Sql Server) is selected. Are you kidding me Microsoft? Include the latest Windows Installer and PowerShell with it. And have some kind of warning in advance that you must have Visual Studio SP1 before installing. People just want the damn thing to install with no problems. These isues are going to put people off from using SQL Server.
I am so sick of these horrid installs. Microsoft just keeps getting worse and worse. Why in the hell should the vs2008 sp1 take THAT long to install. I know 2008 was crap when they released it, but it’s not like this service pack actually fixes anything. Will someone at macrosloth please friggin GOOGLE \quality\.
well at least you are downloading everything and installing them for free:P
I couldn’t believe how overcomplicated the installer for SQL 2008 Express was – the SQL team needs a serious crash course in usability. The essential task at hand for me was “install the core SQL 2008 engine” and they managed to split that into a confusing “installation center” 6-page easter egg hunt for the “install it” link, which then led to a 7-page wizard full of redundant obfuscation. Bleh!
The SQL server and IIS team have been really heading off the rails with convoluted UI’s – they should take a hint from the Windows 7 team. Simplify!