You hit the nail on the head with many (but not all) MS products. I've had the (dis)pleasure of working with SSIS, SSAS and SSRS. SQL Server itself is a pretty decent DB, certainly better than MySQL, but the tools for extending it are just awful. Sure, SSIS is graphical and you can throw together a pretty flowchart that will make managers and bean counters happy at the demo. Then you actually have to do something real with it and find that you can't, for example, deploy a complex package hierarchy to the SQL Server store without manually changing core behavior of your packages, or you can't import Excel files that have blank columns that start having numbers in them because Excel via SSIS insists on guessing the types based on the first 8 rows (only configurable via a registry setting!) and it may break in production without any warning. The list goes on and on. Here are a few more: http://ayende.com/wiki/I%20Hate%20SSIS.ashx?AspxAutoDetectCookieSupport=1.
I've found similar problems in other MS products. Visual Studio is still somewhat of an exception, but probably because it can still get out of your way and let you write code, and it's been around long enough that the good engineers of ages past kept it from turning to shit.