Cross Database Comparisons Made Easy
Significantly reduce cost and speed up migration projects, Cut down hours of cross database validations. Significantly Increase validation test coverage. Jarvis uses AI to automate most of the grunt work in complex cross database conversions and migrations.
Request Demo

HOW JARVIS WORKS

1
Connect
You configure Jarvis with read only access to source and target databases. Jarvis can connect to different data sources like Oracle, DB2, SQL server, and can create data models which contains tables, indexes, columns and other database objects to be compared.
2
Extract
Jarvis then shows the source database and the user can select the tables for validation. The data from source is then copied into Jarvis's temporary storage. The same is done for the target database.
3
Export
Next you export the two databases to Excel. In Excel you can eyeball and write conversion rules to validate if the programmed transformations are correct.
4
Scale
You can then take the excel formula and then Jarvis auto creates the SQL. Jarvis then runs the validation on every record. Giving you 100% coverage and unprecedented confidence.

BENEFITS OF JARVIS

HOW JARVIS SIGNIFICANTLY SAVES COST AND DRAMATICALLY SPEEDS UP DILVERY OF MIGRATION PROJECTS

No Database Corruption

Typically data from source is first exported and imported to target database and then comparison is performed. Which means write operations are happening on production instance. With Jarvis no write happens to any of the databases. The data from the source and target are copied into Jarvis temporary storage which is optimized for validation.

Self-serve

Typically before performing the validation you have to contact the team for the source, and the team for the target and get them to run the conversion rules and then make the source and target availaible for validation. With Jarvis, you directly connect to the source (e.g. DB2) and target database (e.g. SQL server), and Jarvis takes care of the running the conversion rules, extracting the table so you have no dependency on other teams. This dramatically speeds up the validation cycle.

No Performance Impact

Typically, validation are done on the production or dev instances, and that ends up in impacting the performance of the systems. Since Jarvis is a read-only system, the production instances are untouched.

No Cleanup Needed

After the validation, the data imported for validation needs to be deleted. However, this is often forgotten. Unnecessary data in production leads to more maintenance, higher costs, and false alerts. With Jarvis, all these problems are gone because Jarvis keeps the validation data in a separate store from production.

Full Validation Coverage - Each Record (not just eyeball)

Often the business analyst validating the conversion eye balls the results by importing them to excel. They will write an excel formula to get the desired conversion rule and then they just check a few rows. Jarvis has an AI engine which can take the users excel formula, converts that formula to SQL and then runs it on the entire database, and does an exhaustive comparison. So freedom from errors, and validation with confidence.

Faster Validation Cycles

Jarvis uses AI to perform some automated validations. For instance, things like schema, non converted columns, etc are checked giving you peace of mind, and reducing the amount of manual validation

FREQUENTLY ASKED QUESTIONS (FAQs)

Question Answer
What is Jarvis? Jarvis is a software that uses artificial intelligence (AI) to make cross database comparison painless, fast, reliable and error free.
Who uses Jarvis? Jarvis is used by the client or business team that gave the requirements to the dev team which implemented the conversions using SAP BODS.
When is Jarvis used? Very frequently. It is used in dev, QA, and productions. Basically, whenever the development wants some testing done of the conversion rules they wrote, Jarvis can be used to perform that validation.
How do I know if Jarvis is suitable for my company? Any project which involves data conversion and migration. Example of projects are legacy to SAP implementation, migrating to a newer SAP system (for instance implementation of SAP HANA), etc.
What happens when we contact you? We will schedule a web meeting. Give more detail of the product, and then give you enough material so you can get budget approval to make a case to your management for budget approval.
Why did we start Jarvis? SAP implementation projects are long, expensive, and painful. We realized that one of the biggest time sink is validations which are done in an ad-hoc way by each company. With Jarvis our vision was to bring AI based automation and best practice around validation to every company.
How do I get started? To get started purchase a trial license. Get connection settings from your DBAs. Configure the system ( we have tutorials), then complete your validation. Jarvis will stop working after a few validation runs. You have to buy more
How is Jarvis different from other solutions? Jarvis uses AI to increase validation coverage. Jarvis also uses AI to convert excel to SQL so that validation done in excel can be replicates to all records.