In this blog I am going to have a quick look into why anyone would want to deal with obsolete data and then in more detail into the ways to do so. And since I'm targeting a FileMaker audience, some of my statements will be FileMaker specific and may not apply generally to database design best practices. Also, for clarity, this blog is not about backing up your data and backup policies. It covers only practices used within a live application. Regarding key usage, all table examples use a numeric field named '__id' with a unique non-empty validation rule.