Updating real time data
For example, if previously updated fact data using TID value 2, the next update must use a TID value of 3 or higher.Note: You should assign the same TID value to all fact rows that are loaded together. For example, if you have updates available for TID values 3, 4 and 5, you can load them all at once.This step was required to allow the application of changes to data values in the data warehouse tables during the execution of end user business intelligence (BI) queries.When the update was complete, it was necessary to restart the cube in order to rebuild the data caches to reflect the new table values.
To be able to figure out when new features are added, when old features are removed, and which features are just updated, Leaflet Realtime needs to identify each feature uniquely.
To improve query performance, you are recommended to create an index on the TID column. Rules for inserting new rows into a data source fact table Before loading fact data to a dynamic cube, you insert new rows into the fact tables in the data source.
For the initial fact data, the TID column must be set to Null. New rows for near real time updates must adhere to certain rules: When you follow these rules, new rows can be inserted at any time.
Updating aggregate data separately to fact data You can load updates to aggregate tables separately, at a later time, and you can choose when to run these maintenance updates.
To achieve low latency and continue to provide fast performance, queries against a dynamic cube return values based on a combination of aggregate table data and the current completed incremental update of fact data.