SQL, ASP.NET. Is it really that bad to have all the business logic in SQL stored procedures rather than in C#?
So that's having tables in SQL mapped to C# objects. C# does all logic, SQL only does CRUD, nothing else. A practice recommended by Microsoft and others.
A C++ PhD wiz I know thinks it's terrible. My company however, thinks it's more efficient (they've done it with procs for at least a decade now). I don't know any other way.
Thanks
Posted Mar 24, 2015, 2:35 PM UTC
110