Contents
Are stored procedures a bad practice?
Stored procedures promote bad development practices, in particular they require you to violate DRY (Don’t Repeat Yourself), since you have to type out the list of fields in your database table half a dozen times or more at least. This is a massive pain if you need to add a single column to your database table.
Are stored procedures good practice?
Stored procedures are useful for enforcing constraints at the database level. It’s easier to validate a handful of stored procedures restricting access to the database than it is to validate every bit of client code. So this makes them good.
Is the usage of stored procedures a bad practice?
Stored procedures promote bad development practices, in particular they require you to violate DRY (Don’t Repeat Yourself), since you have to type out the list of fields in your database table half a dozen times or more at least. This is a massive pain if you need to add a single column to your database table.
When is one practice is a bad practice?
Sometimes just one practice is bad but more often several are antiquated. Ridding bad practices implies eliminating certain elements from the bundle that don’t make sense any more, thus creating a new business model that represents a series of practices that do fit well together for your customer today 8. Take aim at a chunk of the market
Why are redundant fields and tables a bad practice?
Redundant fields and tables are a nightmare for developers, since they require business logic to keep many version of the same information up to date. This is an overhead that can be avoided if normalization rules are followed thoroughly.
What are the common practices of database design?
You are faced normally with confusing tables, views, columns, values, stored procedures, functions, constraints, and triggers that take a long time to make sense to you. And, once they do, you start noticing many ways to improve and take advantage of the stored information.