Stored Procedures are EVIL

By Tony Marston
2006-09-07

Version Control

It is easy to control all changes to application code by running it through a proper version control system, but those facilities do not exist for stored procedures and triggers. How much damage could be caused if a stored procedure were to get out of sync with the application code? How easy is it to check that the application is running with the correct versions? How much more difficult would it be if the application you were supporting was running on a remote site with nothing more than a dial-up connection?

This is a reason why some teams avoid stored procedures like the plague - it eliminates an area of potentially disastrous screw-ups.

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