Stored Procedures are EVIL

By Tony Marston
2006-09-07


References

• Stored procedures are bad, m'kay?
• One, two, three, or n tiers? (page 3, 7th paragraph)
• Domain Logic and SQL
• Business Logic In Stored Procedures
• Why I do not use Stored Procedures
• Problems with using stored procedures
• Stored Procedures v Parameterized Queries
• The Myth Of Data Integrity
• I inherited a database which contains sprocs (and a lot of other BL)
• Good and Evil in the Garden of Stored Procedures
• Attitudes towards Stored Procedures
• Who needs Stored Procedures, anyways?
• Stored Procedures vs ad-hoc SQL
• The Worst Possible Way to use a Stored Procedure

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