Damn straight I'm not sure what I'm getting into.

I recognize the issue that ORM tools are attempting to solve. I acknowledge that the various tools I've investigated do a pretty good job solving it (to a degree). What I'm having serious trouble getting straight in my head, as a dba, not a developer, how does this change my life? I'm surrendering stored procedures and granular security. Some of that isn't an issue. Performance, for example is identical between a parameterized query and a stored procedure. But, if there is a tweak available to the TSQL that will improve performance when it's problematic, I can apply it to the procedure, but I can't to the query. That concerns me.

I'm being asked to surrender relational data design. Yet, I'm still required to integrate this data with the rest of the enterprise, provide reporting, yada-yada-yada. As near as I can tell, we're just shifting a ton of work into other spaces in order to reduce development time by 10-20%. I just need to understand if that shift is 1-1, for an hour of developer work saved, we're adding an hour to data migration work or if it's 1-.5 or 1-5 or worse?

So,yeah, I'm not sure what I'm getting into. That's why I've been trying to get someone, anyone, to point me to a white paper or case study or decent set of blog entries, about a reasonably large scale application's development, reporting and maintenance over a period of time. I keep finding all kinds of "boy, it sure made development SOOOO easy" stories. That's nice, but development is only part of the pie in a functioning enterprise, especially one that is focused on something other than developing applications.