It's all about the answers!

Ask a question

How can you keep your trend data after migrating data warehouse database to different vendor

2 answers

permanent link
Daniel Moul (4.7k1118) | answered Oct 06 '21, 8:01 a.m.

You (or if not you) then someone who is familiar with database migrations would need to take this on as a project, comparing the table/column definitions between a data warehouse in the source and target database, then transforming the data accordingly.  We provide some pointers on the page you reference on the subsequent PUB row to help you get started. These apply to the data warehouse too:

Use database migration documentation/utilities/practices such as the following: 

Daniel Moul commented Oct 06 '21, 8:02 a.m.

you can think of my post here as a fourth option .

permanent link
Krzysztof Kaźmierczyk (7.4k34997) | answered Oct 06 '21, 7:59 a.m.
There are few options:
  1. Do not migrate data warehouse vendor. You do not have to migrate your data warehouse if you are migrating the database for base applications.
  2. Create new data warehouse with new vendor and switch to this new vendor but keep the old data warehouse. If the users will need trend data from the past, they can create the new reports with the old data warehouse, if they need.
  3. Install the new database but keep the old one as default for some time. Do not disable data warehouse jobs on any of these databases. Use the old data warehouse for reporting. The purpose of installing a new data warehouse is to start gathering trend report there. Once you decide, that you have enough trend data in the new data warehouse, switch to the new data warehouse and disable DCC jobs on the old one.

Your answer

Register or to post your answer.