Import historic data from external source

Question

We are developing a monthly import of employees info. With time data evolves and we want to keep track of historic values.

Is it ok to import data with a time reference (eg: year and month) in order to add new data every time?

I'm asking because I know FDI is not very user friendly with historic data

Sumanth V -Oracle · Accepted Answer

@Stefano_Mazzocca - Yes, importing employee data with a time reference (e.g., snapshot year/month or as-of date) is a common and generally sound approach for maintaining history in FDI/analytics, especially when the source doesn’t provide clean effective-dated change tracking.

Bhaskar Konar · Accepted Answer

Fully agree with you, @Sumanth V -Oracle and Thanks for sharing.

Additionally, if possible, it’s also worth checking whether the source can provide change indicators or effective start/end dates. This can help reduce the need for full snapshots and make historical tracking more efficient.

Hope this help.

Thank you.

Silvio Garber-Oracle · Accepted Answer

I´m glad that I asked. What you mention is a characteristic of every data warehouse based on a star schema model, which in fact is the most used one.
Star Schema vs Snowflake Schema: Differences & Use Cases | DataCamp