Stored Procedures are EVIL

By Tony Marston
2006-09-07

Database triggers are hidden from the application

A big problem with database triggers is that the application does not know that they exist, therefore does not know whether they have run or not. This became a serious issue in one application (not written by me) which I was maintaining. A new DBA who was not aware of the existence of all these triggers did something which deactivated every trigger on the main database. The triggers were still there, they had not been deleted, but they had been turned off so did not fire and do what they were supposed to do. This mistake took several hours to spot and several days to fix.

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