Ready or Not, Microsoft Expands DBA's Role

Ready or Not, Microsoft Expands DBA's Role: "Microsoft hates DBAs. Ask anyone. OK, ask anyone who is a DBA, especially those who don't really support SQL Server.
I have attended my share of IOUG and IDUG conferences in my day. I always enjoyed the performance-related presentations where one could debate the relative impact of locking scenarios and dynamic versus static SQL, or indexing strategies.
Then I attended my first SQL PASS conference about four years ago. It seemed all they talked about was development issues. Where were all the performance geeks, I wondered?
Certainly the answer must be that Microsoft hates the DBA. Then came the CLR. Microsoft was now going to enable developers to run business logic within the database written in any .Net-approved language. Didn't Microsoft know that most DBAs have no clue about most programming languages? How did they expect the DBA to tune and troubleshoot stored procedures and triggers written in languages they cannot understand?
Why is it that almost every demo I've seen for SQL Server 2005 (referred to as Yukon for most of the past four years) focused on integration with Microsoft Visual Studio or how easy it is to build ETL scripts using data transformation services. Do you think it could be because Microsoft hates DBAs? "