Hi Charles.Memorial Day??? Wishful thinking - the summer is ending, not beginning
My only real complaint about the framework is the poor documentation. Andy has been working as a SQL Server DBA for the last few years, so he writes all my SPs. Best practices dictate setting NOCOUNT ON at the beginning for performance reasons. Well, it is not documented anywhere that the framework requires that NOCOUNT be set OFF in order to handle saving data. Mentioning this little nuance in the topic on Table CRUD Stored Procedures might be a good idea, don't you think?
We also noticed that framework calls SP_ExecuteSQL directly - this is a real no no from a security standpoint. I wonder if the framework breaks if the DBA denies access permissions to system stored procedures and tables.