Key Features of MANTA: Current and Past Revisions
Due to popular demand, we bring you another episode from our series “Key Features of MANTA”. This time, we will take a look at MANTA’s ability to automatically report the differences between current and last revisions.
Exactly which differences are reported?
Usually, you are not the only user in your business intelligence environment. Many employees and groups of employees within the company access specific resources, edit database schemas, or just upload new information, e.g.: add new customer records, edit customer information such as addresses or phone numbers, and so on.
When various changes are made in your database, it is possible that some relations within tables are changed or deleted, and that can lead to spare tables suddenly getting “lost” in traffic or being modified, resulting in a change in the course of the data lineage itself.
Suddenly, the data lineage you have been exporting from MANTA doesn’t fit in the database anymore. This could mean that you no longer have an accurate overview of the data being used in your database, or even, in the worst case scenario, that you are no longer compliant with regulations.
Practical explanation of how revisions work can be found in our technical demo of MANTA + Microsoft SQL Server. Take a look (video will start at 5:09, where Lukas starts to explain how revision system works):
We’ve got you covered!
Because MANTA is specifically tailored to meet customers’ needs, we have noticed this point of frustration and have developed a specific feature that allows you to avoid any unpleasant situations in connection with changes to your database. Every time you log in to MANTA, it will let you know what has changed since it last exported data to your metadata management solution. We’ve simply got you covered!
Is there anything else you’d like to know about MANTA? We are always available at email@example.com.