LINQ to SQL - will this be a future of database development?
Since the CTP of SQL Server 2008 there has been much of traffic going around talking LINQ is a replacement of TSQL etc. etc. As you may see that LINQ which is a .NET related language integrated query kind of project that is initiated to standardise data access across not only data sources but also development,a lot of benefit of what a Developer would see.
They may agree that LINQ's benefits include, most significantly, a standardised way to query not just tables in a relational database but also text files, XML files, and other data sources using identical syntax. Also the ability to code from any .NET-compliant language such as C#, VB.NET, and others.
Not many DBAs out there are not happy with this approach whereby the performance of database cannot be controlled due to various SQL architectural constraints and no influence to optimize any of the LINQ related code.
So keeping this mind I was referring (study) through the documentation on Technet and fellow MVP blogs about LINQ, here are few for your reference too:
Simon Sabin's LINQ related blog posts (interesting):
LINQ to SQL – Abtsracting your database.
Whats the score with LINQ to SQL?
LINQ to SQL Gotchas - Using Stored procedures