As a developer I have got to commend a DBA for bringing this up. I very rarely deal with DBA's and am mainly responsible for my own databases.

In my experience most developers develop a product without thought to Entity Life History which is a very simple check on whether data should be created and checks that it is later destroyed (archived).

This is fine at the development stage and will normally stand up to expected usage testing, but the knock on affects of creating data that

1. is never used so there was never a good reason to create it except it existed in the old system

2. is never archived (destroyed) so it slows down querying for more recent useful data.

are larger than most developers give credit to.

Mr Peter Livesey