The Database Design Resource Center

relationships - that doesn't hurt

by john

A huge company, a huge and terribly expensive system. About 300 tables in db wihout any relationships. They were substituted by triggers. Nice?

Comments for relationships - that doesn't hurt

Average Rating starstarstarstarstar

Click here to add your own comments

Oct 07, 2015
If this is NEW
by: Simon Collins

If this is the case then I would say implementing the constraints in triggers rather than in application code was the right thing to do at the time.

buy soundcloud plays

Jun 22, 2015
Good post NEW
by: Arturo Lesch Sr.

Thanks for your brilliant articles! Your niche site is great!
May I publish your article on my site?
I will link for you as an author of this article!

Many thanks for answering!

Jun 10, 2015
Education NEW
by: Anonymous

For the countries in which he has to act as intermediary, he must be able to communicate well with the help of in the native language of the both countries so that there should no gap exist between the understandings of any of matter.

Oct 03, 2009
To be fair
by: Will

To be fair not many DBMSs supported declarative foreign key constraints before the 90s - but some did support triggers before then.

So it might be expected that older systems may not have foreign key constraints in place.

If this is the case then I would say implementing the constraints in triggers (rather than in application code) was the right thing to do at the time.

However it would make sense today to replace the trigger implementation of the foreign key constraints with declarative constraints.

That being said, the support for declarative constraints in SQL is still far from adequate and you still have to do far more in triggers than would be ideal.

Sep 27, 2009
They may be don't really crazy that you think
by: Anonymous

Some kind of people usually don't like relation ship. Relation ship is not good as you think.
example. if you querry db with a db have many many relation ship table. it will be slow down. but when insert or update, it really faster and easy mantain. So, according your goal. design your db correct.
this is my idea

Dec 19, 2007
by: Anonymous

Yes, that's how unexperienced designers misunderstand the built in powers of the DB. Crazy story though; I wonder what made them do that...

Click here to add your own comments

Join in and write your own page! It's easy to do. How? Simply click here to return to Worst Database Design Experience.

Exclusive interviews with:
Steven Feuerstein, PLSQL expert
Donald Burleson, Top IT consultant

Free eBook

Subscribe to my newsletter and get my ebook on Entity Relationship Modeling Principles as a free gift:

What visitors say...

"I just stumbled accross your site looking for some normalization theory and I have to say it is fantastic.

I have been in the database field for 10+ years and I have never before come across such a useful site. Thank you for taking the time to put this site together."

Mike, USA

Read more Testimonials

Database Normalization eBook:

Database Normalization eBook

Copyright © / Alf A. Pedersen
All rights reserved.
All information contained on this website is for informational purposes only.
Disclaimer: does not warrant any company, product, service or any content contained herein.

Return to top

Copyright acknowledgement note:

The name Oracle is a trademark of Oracle Corporation.
The names MS Access/MS SQL Server are trademarks of Microsoft Corporation.
Any other names used on this website may be trademarks of their respective owners, which I fully respect.