Migration
If you already have documents stored in your database before you enable temporal versioning for that document type, the documents will be migrated when first loaded. The non-temporal document will be rewritten as a temporal document that was always effective (starting at DateTimeOffset.MinValue).
The bundle does not convert all of your documents automatically. If you want to ensure all documents are participating in indexes correctly, you need to go through your database and load each document at least once.
If you decide to disable temporal versioning for one or more document types, The bundle will not make any changes to your data. The existing "current" documents are immediately usable, but you may want to delete any temporal revision documents that exists so they don't interfere with your indexes.
Introduction
Home
About Temporal Versioning
About DateTimeOffset
Setup
Installation
Enabling The Bundle
Client Initialization
Configuration
Migration
Usage
Specifying Effective Dates
Basic CRUD Operations
Temporal Activation
Querying Temporal Data
Querying Dynamically
Querying a Static Index
Map/Reduce of Current Data
Advanced
Temporal Map/Reduce
Temporal Relationships
Guidance
Getting an Audit Trail
Practical Application Guidance
Reference
Misc