But to answer your question anyway....I haven't seen anything that has caused me to reconsider the use of SPs as a starting point. That is the colossal irony of LINQ - if you're reading other blogs and newsgroups, you'd know that there's an equal or even greater excitement about the ability to query XML or custom objects or typed datasets more effeciently and productively.

Yes, and to do it *in-memory". Not at the database. QED.

The thing about pulling one quote from one person - it's just so easy to refute. Why did MS implement more stored procedure functionality in SQL 2005 and have already committed to doing more in the next version of SQL???

It's not a "SP versus in-memory processing" scenario. I use SP. I want in-memory processing *as well* not *instead of* SP. If SP is best, I want to use SP. If Linq/change-tracking is better, I want to use that. Above all, I want to take the opportunity in 2007 to make sure that my hypothetical plan for NET is the very latest and offers best longevity.

John, I honestly don't know if you're serious or just looking for a good verbal sparring partner (as you've already acknowledged to me that you're sometimes up for a spirited discussion). Maybe if you'd clue me in up front, it would help.

Maybe we should just keep the personal out of it and focus on the technical?