Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I have an application that uses data from a DB that only has the past 30 days worth of data at any given time. Because of this, we use delta loaded QVDs to build the application with around one year's worth of data.
The problem is sometimes our data is changed and thus only the past 30 days worth of data is updated. For example it will look like:
Data Month/Year | Sales Region | Sales Region Leader |
03/21 | West | Patrick Layton |
04/21 | West | Patrick Layton |
05/21 | West | Patrick Layton |
06/21 | West | Patrick Layton |
07/21 | West | Carl Peter |
When I need it to look like:
Data Month/Year | Sales Region | Sales Region Leader |
03/21 | West | Carl Peter |
04/21 | West | Carl Peter |
05/21 | West | Carl Peter |
06/21 | West | Carl Peter |
07/21 | West | Carl Peter |
Is there a solution to this without hardcoding and limiting the manual work? I know I can create a mapping table Excel document but these record updates happen often and I'd rather not have to keep adding the new updated records to an Excel document in the future each time it happens.
I think your doing the mapping at the last stage !!!
On every delta load do the mapping and store it in to QVD so that during that point in time what ever the mapping is their will get updated else you need to update the mapping key with the time stamp so that while doing the mapping it would take that specific month value
I think your doing the mapping at the last stage !!!
On every delta load do the mapping and store it in to QVD so that during that point in time what ever the mapping is their will get updated else you need to update the mapping key with the time stamp so that while doing the mapping it would take that specific month value