I've installed SQL Server 2000 at least 200 times in my career and its seldom ever given me any heartburn. Then along comes SQL Server 2005 and its installation is the biggest consistent pain in the neck i've ever worked with. Why exactly did they have to rework something that was already working?
Today I had to install 2005 for another component installation and after at least an hour it finally reached the point where it was installing the workstation components...and it sat there...and sat there...and sat there - for at least an hour. I didnt want to kill the installation, because i've done that before and that caused 2-3 days of hacking and cleanup.
So, i started searching and eventually ran across something i had forgotten - that if the 2005 installation hangs, try disconnecting the network cable - which, after another 20 minutes, caused the install to pick up and finally finish.
What kind of ridiculous solution is that for a something that's supposed to be enterprise-class software?
good grief
Subscribe to:
Post Comments (Atom)
Posts
No comments:
Post a Comment