Stored Procedures are EVIL

By Tony Marston
2006-09-07

Stored procedures take longer to test

Business logic in stored procedures is more work to test than the corresponding logic in the application. Referential integrity will often force you to setup a lot of other data just to be able to insert the data you need for a test (unless you're working in a legacy database without any foreign key constraints). Stored procedures are inherently procedural in nature, and hence harder to create isolated tests and prone to code duplication. Another consideration, and this matters a great deal in a sizable application, is that any automated test that hits the database is slower than a test that runs inside of the application. Slow tests lead to longer feedback cycles.

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

Stumble It!

	4 Votes

Showcase Your Tutorials

You might also want to check these out:

Using MySQL Functions for More Efficient Web Applications
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.

Leave a Comment on "Stored Procedures are EVIL"

You must be logged in to post a comment.

Link to This Tutorial Page!

	Helping ordinary people create extraordinary websites!
		SIGNUP LOGIN