>>>Is there any benefit to converting my data access layer to Linq To SQL?
>>
>>You may want to look past Linq to SQL to another technology like Entity Framework or NHibernate. One of the best advantages I've found is that Linq keeps me in the IDE, and I don't have to be switching back and forth between VS and SSMS. I also find that I spend a LOT less time writing Stored Procedures and more time focusing on creating a rich domain model.
>
>I have been spending a lot of time in stored procedures lately. More than once in a while its limitations make me chafe. It reminds me -- and this is not a warm memory -- of COBOL. I hope major improvements to both T-SQL and the SSMS IDE are somewhere in the pipeline.

There are some annoying parts, but it is a very capable language. I've been working intensely with it since SQL Server 7 and haven't found a situation where I could not accomplish a data task. Granted there are environments that make some things much easier, but in the end T-SQL by nature of the data engine will run most data tasks faster.