Question: I just started using Linq to SQL, and it just occurred to me that I don't really need any sprocs in the database since i can do all the data access through Linq to SQL. 

Is there any reason to write sprocs with Linq to SQL?

Thank you.

Answer: 
Much less, IMO, but there are still occasions where using stored procedures or table-valued functions can useful. Of course, LinqToSQL doesn't preclude using stored procedures so you can still use them if desired. For example, I've used table-valued functions to do parameterized queries against table joins to support multi-variable filters. This can greatly simplify your code and gives you the ability to optimize the query.
I fear you've just walked on a religous mine!

Stored procedures or not is a very hotly debated subject, and often (in my opinion) boils down to a fight between DB/SQL specialists on one side and 'vanilla' developers on the other. Each side trying to get as much of the duvet as they can.

Check out this link, [Stored procedures are bad, m'kay?](http://weblogs.asp.net/fbouma/archive/2003/11/18/38178.aspx) and the ensuing LOOOOONG debate.