To Migrate, or Not to Migrate, the Report?
When migrating data, you can get into some pretty tricky situations. It is always tough to decide what data to migrate and what not to. MANTA can help you decide as well as reveal some crucial relations within your environment. Read on to learn about the surprises you may find in your DWH.
While one of our customers was dealing with their data migration project, something unexpected came up. When MANTA helped the customer see the relations and detailed dependencies between all the reports, the customer came to realize that multiple reports in the environment were sharing tables with each other. But the reports were of different levels of importance.
MANTA’s ability to show all the dependencies within the environment prior to migration helped the customer approach the problem proactively as a complex matter. This saved the customer a lot of time and allowed them to avoid future complications. Otherwise, the customer may have found these relations much later, such as after the migration when one of the reports stopped working properly. Then they would have needed to go through thousands of tables manually to see where the problem was. MANTA enabled the customer to be prepared and gave them the opportunity to make the necessary decisions ahead of time, before any problems occurred.
Multiple reports in the environment were sharing tables with each other. But the reports were of different levels of importance. In one case, the customer wanted to migrate a report to the newly established cloud because it was a frequently used report that was worth keeping. But the report shared some tables with another report that had much lower priority for the customer’s company. However, regardless of its lower priority, it wasn’t exactly a report that could be deleted. It was still used occasionally.
The customer could migrate all the reports and tables involved, but that would inconveniently inflate the amount of data being migrated. Alternatively, the customer could skip these reports and tables and not include them in the migration, but then they would not be able to use the reports in the newly established cloud environment. The customer could duplicate all the data, but what if something changed? Having the same data in multiple places always requires effective synchronization to make sure the data is identical and up-to-date everywhere, which is usually a really complex problem.
So what should the customer do? Have you experienced a similar situation, or are you afraid that this is your case too and you need MANTA’s help to find out for yourself? Contact us at firstname.lastname@example.org or join the discussion under our post on social media!