IMO MS did build a great product with wanted technology, but lost the battle before it had begun because of the lack of managebility aids !
Just considering you may have a 50GB database with only 30MB of accounted data blows ones socks out.
All the rest of space was use by a single queue, because the sproc handling the simple processing just took to long and couldn't match the load.
Did you ever try to purge a queue because you queue readers weren't able to cope with the load ? It surely isn't a truncate like operation.
(I know it shouldn't be considered normal, but you have to be able to intervene quickly to get your instance back on track and take your data loss.)
Yes , security is a pain, but it is very good ! Once you've set it up it is rock solid !
For once MS did what is most other respected rdbms vendors do by default. i.e. assume your DBMS engineers first take on the knowledge before trying to run the system, and take time and energy to test and write usage guidelines before implementing in prod.
The missing GUI is one example for this.
I hope to get to testing it with SQL2008R2 very soon.