SQL Server 2008 is the worst installation experience ever

Question

Sorry but you guys have really messed up with SQL Server 2008 installation.
I've been using SQL server since 6.5, so I would classify as a fan.  We were looking at upgrading from 2005, which I was quite pleased with.
The installation experience is the worst I've ever experienced.  I am a computer expert, and I couldn't figure out how to install it properly.  Why is it that when I downloaded SQL Server Management Studio Express 2008, it seems as though it wants
to install the full database?  Why is it when I was asked if I wanted to install a new version of SQL Server 2008 or use a previous install, when I chose previous install, it said that an instance ID was missing, but there was no way to specify anything
else?  It drove me crazy.
Why are there so many requirements and restrictions for the installation, when all I want to do is install Management Studio?  It's intolerable and makes me never want to upgrade to 2008.  Why is the process so terrible when Microsoft is supposed
to have the best UE people in the business? 
You guys did a really terrible job on this one.

Answer 1

We have not tried to cluster 2012.  We used to cluster; however, we were not prepared to manage the added complications.  The result was that our non-clustered servers had better uptime.  We used to joke about how many 8s we were
getting with our cluster.  (To be fair, it did not help that we had a 7x24 SLA with only 8-5 staff.  When the cluster fails to failover, it can be a long time before it is fixed.  We eventually got the kinks worked out.)  
I understand the frustration.  Excellence and stability can be achieved, but product lifecycles can punish those who seek such qualities.  Product changes and shorter support lifecycles produce revenue for MS, so I don't see this getting better. 
There will be a new OS, new SQL, and a new set of problems the next time around. 
I expect things to get worse until we get pushed into the cloud.  A stable environment in the cloud is profitable for MS and clients.  I do not think this is the case now outside the cloud.  Upgrading applications to remain
on supported products is very costly.  And about the only business benefit of the upgrade is that the product remains on a supported platform and gets security updates.  Sort of sound like that blackmail virus?  I'd rather pay to have a
patch for new features and focus on application upgrades that improve business processes.  Now bug fixes can require a major version change - which will have new bugs.  I'm ranting because of some head pounding
I've done this week due to a hard coded limitation introduced in SQL 2012 by design.  I'll replace the process, but I wonder how long it will work as my SQL related PSH often breaks with a new version of something.  I'll
stop now. Where'd my Prozac go?  Next week is new week, life is good, everything will work,.... 
PS I actually enjoy the work and think MS products are decent; however, our environment does seem to be more frail and less stable due to MS product changes - even if the products are getting better.  Better is worse - what an odd thought. 
Randy in Marin