>Hi Mike,
>>
>>I know where you're coming from - I came from the same place 6 months ago. I've since been fully commited to learning an ORM and haven't looked back. Most (maybe all?) ORMs use parameterized queries which eliminates SQL Injection capabilities. You can still create and call Stored Procedures from ORMs, but it's kind of a low value (unless it fits your requirements) task.
>
>I am wondering however too about the benefits of a SP being outside the application domain and thus allowing updates, tweaking, or modifications made more readibly. But then I think, they should be well established by this time and probably many changes require a change in the program as well. I don't know now but still pondering.

In my DBA role I frequently make back-end changes to table structures, functions, and constraints. Since all my major data handling is done through stored procedures, this rarely requires application changes.

This is my primary reason for using Stored procedures almost without exception.

>
>Stored Procedures are certainly easy enough but I don't have a complete wrap around on the EF impact side yet. Working on it.
>Thanks for your comments.
>Tim