No contridiction from my viewpoint.  SQL and T-SQL aren't the same thing.  I don't think SQL is going anywhere since it does what it does quite well, but the way we access and manage the results from queries, loops, variables, error handling, transactions, etc (i.e. T-SQL) will likely shift to CLR in the long term.  If you haven't programmed C# or VB.net, you will likely fall in love with them once you see how much easier data manipulation can be in a language that was designed for it.

I don't have a problem with someone disagreeing with me since my points are only speculation, but that first poster who called me silly either didn't read my post well and missed the point or has a screw loose.  I am not being irrational.  My point is that anyone who uses both TSQL and some other next gen language will tell you that TSQL is weak in many areas and it is time to get something better.  It isn't marketing or some spitball idea (at least not completely).  Programmers have been asking for a real language in SQL for quite a while.

The original author of the story made it sound like CLR wasn't "all bad" and I believe that CLR integration is great.  That is where our points divulge.  My additional thoughts about TSQL going the way of dino are just thoughts that reminded me of the old COBOL switch (back when more lines of code were written in COBOL than any other language).