Stored Procedures are EVIL

By Tony Marston
2006-09-07


It mangles the 3 Tier structure
Instead of having a structure which separates concerns in a tried and trusted way - GUI, business logic and storage - you now have logic intermingling with storage, and logic on multiple tiers within the architecture. This causes potential headaches down the road if that logic has to change.

Tutorial Pages:
» Stored Procedures are EVIL
» Stored procedures are not as brittle as dynamic SQL
» Stored procedures are more secure
» Stored procedures are more efficient
» The company has paid for them, so why not use them?
» Application code or database code - it's still code, isn't it?
» It mangles the 3 Tier structure
» Stored procedures are a maintenance problem
» Stored procedures take longer to test
» BL in stored procedures does not scale
» Stored procedures are not customisable
» Database triggers are hidden from the application
» Version Control
» Vendor lock-in
» References

Related Tutorials: » Installing MySQL on Windows » Implementing High Availability in MySQL » MySQL Database Handling in PHP » A Flexible Method of Storing Control Data » Exploring MySQL CURDATE and NOW. The Same But Different. » Creating a PostgreSQL and MySQL driver