>>>I use a lot of SPs and so do a lot of other people that hit the data I find I need to have the backend handle a lot - especially defaults
>
>Yes, if several people share SP's then the defaults make sense.
>
>My first .NET apps used SP's almost exclusively as I did with VFP but I've moved toward doing more in the middle tier because I have to be there anyway and the datasets are so slick to work with.

I don' think it is so much the sharing of the SPs as the sharing of the tables. We don't use SPs as much for CRUD from apps as for serious data munging - creating real time updates to hundreds of tables with no UI but all run by back end batch jobs. Some of these run five or six times a day with no human intervention.

Since nulls are virtually never allowed, without default values, there is always the danger that adding a column or doing s omething else to a table will result in a whole lot of other code that enumerates columns will attempt to stick a null in on an update. It also means requiring every SP that touches the tables accounts for providing blank values.

Denis Gobo, our DBA, has made a believer of me on a lot of this stuff. I had just never even seen an environment like this before. I have become pretty excited about what one can do with set-based processing and I am sure the next time I design the UI and middle tier of a .NET app I'm going to look at it with different eyes.