Minor changes are by default collapsed in the page history.
No changes
The page does not exist yet.
Failed to load changes
Version by on
Leave Collaboration
Are you sure you want to leave the realtime collaboration and continue editing alone? The changes you save while editing alone will lead to merge conflicts with the changes auto-saved by the realtime editing session.
History, configuration, and other database objects
Other than the reference tables, there are tables and associated objects that store history data as it is collected, history data after it has been compressed, discovery, and journal data.
These tables and their indexes should have enough database cache memory allocated for their use to allow the hourly Performance and Availability history compression process to complete in a reasonable time (see the History compression details table in History compression) and support user queries, such as ad hoc reports that return data in a user-acceptable time frame.
As history and journal data are data that accumulate over time, capacity planning must be routinely performed. Keeping statistics current and the frequency and type of reorganizations are dependent upon the DMBS type.
