> if they don't contain too much logic or complexity. I think this is the catch. Most folks who are arguing against SP have been burned by huge complex stored

> if they don't contain too much logic or complexity. I think this is the catch. Most folks who are arguing against SP have been burned by huge complex stored procedures with nested dependencies with deeply intertwined business logic and rules. I completely agree that you shouldn't use a SP in that way. But to help perform maintenance, or to audit, or perform data correction all make sense when kept small and simple.