Honestly, not 100% sure... I know you can called Stored Procs, and from this post on SO it seems like you can: http://stackoverflow.com/questions/10292695/how-to-pass-datatable-as-a-parameter-to-stored-procedure-by-not-commiting-the-cu

It's funny how things change. 6-8 years ago I bought your book and it was my bible for awhile - then I started to try to unwind from the relational database paradigm. I started using ORMs and saw the benefits, but also saw the limitations. Now I'm trying to steer to a NoSQL approach. Not that I have anything against SQL Server and relational database design - I just feel for the systems I work on, and the methodologies I use, I can deliver much much faster if I don't have to worry about persisting to relational data.

YMMV, obviously.

I'm still coming straight to you next time I'm in a SQL Server bind, though. :-)

(Sniff) You've crossed over into the dark side.

I know a few people in NY who are working consistently with NoSQL. Some days they love it, some days they curse it, but then again, I'm the same way.

The reason I asked about data tables and procs - in SQL 2008, you can now pass a datatable as a parameter to a stored proc. But there are some ORM tools that don't support it, so that's why I was curious.

My general opinion, though others might thing differently - I think those tools are almost a standard for OLTP applications. Once you get into data warehousing and analytic applications, it's sort of "hit or miss" and every situation will be different.