Can the Temporal tables functionality in SQL 2016 be utilized within a geodatabase? Or will that cause problems and we should just stick to Editor Tracking and Geodatabase Archiving?
Backstory: a customer has concerns with data integrity and desires a way (independent if possible, via the sql temporal tables) to track if changes are made, what they were, who did them and when they occurred. The first item is what we'd need archiving for, and the others are handled via editor tracking. Again, just seeing if using the sql temporal tables are even an option. Thanks
