In August I blogged about using the new SQL Server 2016 temporal tables for a client requirement. It did everything they required and more. The time machine worked great. But the I started questioning the client requirements and what where thinking of delivering. This is an organisation with developers, but no full time trained DBA. A few accidental DBA's. Who could or would be able to understand temporal tables moving forward? Would it just be forgotten until one day it broke. Sometimes you need to think about who is going to maintain this environment into the future. After discussions with the team we decided that temporal tables were, in this case, overkill. We went with a more basic, simple solution (using the KISS principle) and better/easier for the client.