![]() So all I can do is relay my own experience in a similar situation. Specific advice is difficult without knowing more about the situation. ![]() Hi ZZ-Soft - there are a few gaps in requirement that you have layed out here. This gave the added bonus of Inventory projection reporting too 12 months into the future.Ĥ2 Sight Holistic Data Warehousing:. This DW used monthly and daily loads of inventory from the source system along with future projected changes of inventory from the MRP. However with data such as this there is the proviso that it cannot be accumulated across time - being balance data. I have built a data warehouse with both daily balance record and monthly balance records, enabling the user to toggle between the two. transaction) then have you considered bringing all inventory transactions across to the DW (or staging database) instead of balances? If the requirement is to track every single change (i.e. If an everynight snapshot is enough detail then use the staging database to do the inventory change analysis for loading into the final DW Or is your requirement to track every change down to a transactional level? ![]() Have you given thought to building in MS SQL a staging database or secondary data warehouse in MS SQL that takes a literal copy/snapshot of inventory every night?
0 Comments
Leave a Reply. |