>>>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.
>>>
>>>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
>>
>>I use NHibernate and I know it generates SQL itself, and oftentimes creates more optimized SQL for a particular situation. I would lose that ability if I use Stored Procedures.
>
>I have no experience with nHibernate, but I have heard good things about it. It wouldn't take much to create more optimized SQL than what I could write. :-) I am a fantastic database data designer but write very little in the way of complex SQL.
>Tim

That's my POV also. I can write a mean SQL statement, but why should I? SQL is only more thing that I have to learn and know and keep up on. Why not rely on somebody who is a heck of a lot smarter than me?

Plus, all I have to do is make one config change and all SQL generated is updated to take advantage of new features and functionality. It's drastically reduced my development time.