I am currently working on a financial Risk data warehouse. For my collateral dimension, I am souring the data from one source system. However, after further research by the business analyst, we found a legacy application that also holds collateral information which the bank also needs in the data warehouse. Bar a few common attributes that both source systems share, the legacy application contains a lot more attributes than what is defined already in my current collateral dimension. What is therefore the best way to onboard this new information in the Warehouse? I was thinking of extending the current collateral dimension but then would I need to do this every time I find a new source, which is very likely given the size of the bank. Alternatively is it better to create a new dimension called dimCollateralAdditionalInfo and add the extra attributes there?
Multiple sources for dimensions in Data Warehouse
217 Views Asked by Eseosa Omoregie At
1
There are 1 best solutions below
Related Questions in DIMENSIONAL-MODELING
- Does Power BI provide an OOTB Geographical Dimension Table
- Indexed parent-child hierarchy table to fact table
- Model the number of available spots in dimension or fact table?
- How to build Dimensional model for commission received and return
- Is combining a Junk Dimension with a Conformed Dimension in a single table advisable for efficient data management?
- How to model fact table if its column connects to different dimensions based on record type?
- Power Query - Data model for multiple dimension tables with start and end dates
- Dimensional Modeling: Joining Dimensions together without a Fact Table
- Building dimensional model from multiple sources
- How to handle order line level dimension when used along side a Order level measure?
- How to model a header detail level granularity table alongside a header level fact table when a certain dimension is only applicable to the header?
- How to model a header detail requirement when header has values that cannot be apportioned to details?
- In a dimensional modelling context, is it good practice to have a dimensional attribute which is derived/calculated from a fact table?
- Not quite understand a concept in Kimball's dimensional modeling
- How to deal with multiple facts in dimensional modelling
Related Questions in STAR-SCHEMA-DATAWAREHOUSE
- INSERT a single row in fact table
- How to deal with multiple facts in dimensional modelling
- PostgreSQL as OLAP setup
- PostgreSQL ON CONFLICT add new entry with new timestamp
- Bridge table for many-to-many relationship
- Stream data into BigQuery data mart with three different dataflow jobs, get correct surrogate key for the fact table from dimensional tables
- Data warehouse modling - to use ID or text in a dimensional table
- Dimension Fact tables issue
- Advice on basic star-schema design (Date dimension)
- How to join dimension tables while populating a fact table if business key of one dimension table is not in the other joining table?
- Many-to-many from relational design to dimensional design
- How to fit a separate table in data warehouse model?
- Whether sales (fact) table should be made to have the userid from customer (dim) table in dimensional modeling?
- Should I use multiple fact tables for each grain or just aggregate from lowest grain?
- Designing a DW Model Diagram
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Popular # Hahtags
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
As we always say that a DWH model is evolutive in the time since new business requirements can appear over time. The most important thing is to check if the new attributes are worth to be added and if they present an analytic axis.
You can store all the information in the dimCollateral and you need to think to manage this dimension properly in terms of optimization (indexes, data types...)
Or you can create an extended dimension dimCollateralExtension containing the additional info and it will have a one to one relationship with the master dimension dimCollateral