LINQ vs TSQL - Where it is going?
There are few discussions flying around that Transact SQL will cease to work as LINQ is round the corner and also interesting discussion about impact on C# here.
As LINQ is more kind of development language as Microsoft promoting for develpers, IMHO it is not a replacement for TSQL at all. There are some improvements in LINQ as compared to TSQL and vice-versa. You could take more advantage with the improvements in T-SQL (SQL 2008) are the MERGE statement, OVER() PARTITION BY for aggregate functions, multiple value inserts etc. There may be instances where Developers might deploy LINQ on the application than to TSQL for the ease of GUI features. Within the SQL SErver TSQL is under-cover language which is a native conversation language, whereas LINQ to SQL uses TSQL inside!
No doubt that Microsoft is investing a lot in TSQL & LINQ as a seperate, but TSQL is a server-side programming language with fullest advantage along with the full support on client-side. You might see from the SQL Server 2008 June CTP and Katmai BOL about the TSQL enhancement along with deprecated features, including the new date and time data types and related built-in functions, table-valued parameters, the MERGE statement, grouping sets, INSERT with nested DML, and many more. Most of the above enhancements are available in the .
At the moment, I don't have much knowledge in LINQ to addup, but I will be adding more about LINQ in future blog posts here.