Recon FAQ
Questions before a technical walkthrough.
A concise view of how Recon compares data around existing workflows, the current supported systems, and what an evaluation establishes.
Product, deployment, integration, evaluation
Product
What is Recon?
Recon is a data reconciliation product for comparing data between Oracle, SQL Server, and Databricks. Teams configure checks around an existing data workflow and review the outcome when source and target data do not match as expected.
What problems does Recon help investigate?
Recon helps teams investigate whether a data load or replication event produced the expected result. Depending on the configured check, it can help identify count differences, key coverage issues, and selected data-value differences.
Which systems does Recon support today?
Recon currently supports Oracle, Microsoft SQL Server, and Databricks as source and target adapters. Support is deliberately stated in terms of these current adapters; a discovery session should confirm the specific source, target, and data-access constraints of a prospective deployment.
Does Recon replace a data pipeline, ETL tool, or data-quality platform?
Recon is designed to sit around an existing load or replication workflow. It provides a controlled reconciliation step before and after that workflow; it does not move data or replace the orchestration and transformation tools a team already uses.
What can Recon compare?
Recon supports configurable checks for the questions a team needs to answer when something does not match.
- Expected record counts
- Key coverage, including gaps or duplication
- Selected data values
What happens when Recon finds a mismatch?
Recon records the outcome and gives the team a defined starting point for investigation. The exact review process is agreed for each deployment. Recon is not designed to make business-data changes automatically.
Deployment and access
Where does Recon run?
Recon is intended for controlled deployment in the environment chosen for the data workflow. Deployment planning confirms the requirements for the specific evaluation.
How do approved teams review results?
Results review is configured for the teams approved for the deployment. The technical walkthrough confirms the review experience and access needs for the intended workflow.
Integration
How does Recon fit into an existing data workflow?
A typical integration places Recon around an existing source-to-target load or replication workflow. The evaluation maps the right check to the point in the workflow where the team needs confidence.
Does Recon modify source or target business data?
Recon compares configured source and target data. It is not designed to make business-data changes automatically.
Evaluation
What should we bring to a technical walkthrough?
Bring one representative data workflow, the expected checks, and the team that will evaluate Recon. Do not send credentials, production exports, or sensitive data through the website contact channel.
Is Recon available as a trial or with public pricing?
Evaluation and commercial terms are arranged through a technical walkthrough. The first conversation establishes the reconciliation scope and the product capabilities needed for the intended workflow.