Is it advisable when setting up relationships to enforce referential integrity as a default and then remove only when and if required?

Hi Tim,

Referential integrity is very powerful when used in the correct context. I would not suggest using referential integrity as a default, unless you are very clear about what you are wanting to enforce. Not all tables need or require it, so I would suggest leaving it off, until you know you need it. This should ideally be built into your database plan, so that you are aware of its requirement prior to building the database.

ie - if you know that you want to ensure that a client number exists, prior to creating an order, then enfore referential integrity.

If you are in the design phase of the database, you might find it frustrating to enable all the referential integrity, only to find that it hinders your development progress.

Regards

Richard