on 08-02-2016 7:02 PM
I'm wondering the best way to do this (I do not have a repository)
I'm on 16.5
I have a model for my Data Warehouse that contains both my staging tables and my DW tables. As I add more tables I realize it would be easier to manage releases to the data base with two separate models.
Should I:
1. Just make a copy (Save As) and delete the unwanted parts from each copy?
2. Generate a new model from the current one and then delete the unwanted parts from each?
3. Is there a 3rd option
Keeping in mind that I want to preserve the lineage from the LDM to the PDM DW tables. The staging tables have no such lineage (as they are clones of source tables from a COTS system) and I may or may not document Source to Target mapping from the staging tables to the DW tables in PD
Hello Jane
Whatever you do, don't use 'Save As' to create a new model, as the new model (and the objects it contains) would have the same internal ID (GUID) as the original, which will cause problems later on, especially when you try checking the new model in to your repository - it'll think it's the same model, as it has the same ID.
To create two separate PDMs, do the following:
There is a third way - create a separate package in your PDM to hold the staging tables, then drag those tables into the new package. If you have all the staging tables on a single diagram, here's a shortcut - right-click the diagram in the browser and choose 'Convert to Package'.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
78 | |
9 | |
8 | |
6 | |
6 | |
6 | |
6 | |
6 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.