On this forum people often talk about known best practices and only using stored procedures for UI interface. Is there a book that discusses these known best pratices and gives strategies for using them?

How about data checking and business logic. Where / how are people splitting the responsiblity for data validation and rules? Is it all in SQL or should the UI still be doing some initial checking before the data is passed to the SP for updating?

I am also curious about people's methods of naming stored procedures to organize them. If stored procedures are used for all UI then on a large database there would be hundreds (or perhaps thousands?) of procedures.

TIA.