title: Does LINQ To SQL provide faster response times than using ado.net and oledb?
body: <p>LINQ simplifies database programming no doubt, but does it have a downside?  Inline SQL requires one to communicate with the database in a certain way that opens the database to injections.  Inline SQL must also be syntax-checked, have a plan built, and then executed, which takes precious cycles.  Stored procedures have also been a rock-solid standard in great database application programming.  Many programmers I know use a data layer that simplifies development, however, not to the extent LINQ does.  Is it time to give up on the SP's and go LINQ?  </p>