4 ms·
but it's ASP and SQL and most of the business logic is in SQL stored procedures. Can someone explain to me why this would be considered a bad thing?
by Pamar 10y ago
but it's ASP and SQL and most of the business logic is in SQL stored procedures.
Can someone explain to me why this would be considered a bad thing?
- 0xfeba 10y agoLet me be more clear: The entire application is written in SPs. They have a 3 tiered arch, but the FE and MT see 5% usage and the DB sees 95% usage. And they constantly have timeouts, table locking issues, errors, CPU usage problems, etc. I receive, literally, 10,000+ emails a month from automated error reporting from the DB servers. Luckily it's not my project so I just have a rule to delete all of them.