I haven't written new code that uses stored procedures in the last few years. They are a real pain to maintain in an agile / continuous integration / TDD environment. It's much easier to use an ORM tool like LLBLGen or NHibernate and push an updated application . The EF and Linq fall short in places where other ORM tools are stronger (more mature?).

If a third-party needs access to data then they do that with Web Services. No one gets near the database!

(If there was a realistic need for data access or stored procedures then I'm happy to look at them individually, but in most cases they are not as necessary as people like to think. The performance and security aspects of stored procedures are overblown.)

-Brian (an ALT.NETer)