Stored Procedures are EVIL

By Tony Marston
2006-09-07

BL in stored procedures does not scale

If all the business logic is held in the database instead of the application then the database becomes the bottleneck. Once the load starts increasing the performance starts dropping. With business logic in the application it is easy to scale up simply by adding another processor or two, but that option is not readily available if all that logic is held in the database.

If you have a system with 100's of distributed databases it is far more difficult to keep all those stored procedures and triggers synchronized than it is to keep the application code synchronized.

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