ArcXA is a project-saving necessity.

ArcXA is a project-saving necessity that hits the nail on the head.

ArcXA needs read access to the target system's metadata catalog (information schema, data dictionary, or equivalent). That's straightforward for all seven platforms, but enterprise firewall and credential governance requirements vary — worth capturing as a phase-one dependency in any ASC engagement scoping conversation.

ArcXA  - Mapping is the exact practical reality that derails migration timelines during the Architecture and Scoping Conversations (ASC).

Migration is a governance, access, and security problem. Teams mistakenly treat database migrations strictly as an ETL data-pipe problem. In reality, it  

Equitus.ai ARCXA relies heavily on deep, active metadata catalog crawling (INFORMATION_SCHEMA, sys catalogs, data dictionaries) to map the knowledge graph of relationships, views, and stored procedures before any data moves.

Mapping secures those structural permissions and maps out network/firewall clearance in Phase One, the migration stalls before the first table is indexed.

The blueprint below details how ARCXA interacts with the metadata catalogs across all seven platforms, paired with the exact phase-one firewall and credential governance requirements you need to capture during scoping.

1. Cloud & Lakehouse Platforms

Snowflake

• How ARCXA Extracts Value: ARCXA queries the SNOWFLAKE.ACCOUNT_USAGE and INFORMATION_SCHEMA shares. It targets tables like TABLE_CONSTRAINTS, REFERENTIAL_CONSTRAINTS, and STAGES to build structural data lineages.

• Firewall & Network Scoping: Snowflake is entirely cloud-native. ARCXA requires network egress to the Snowflake API endpoint URL. You must configure Network Policies in Snowflake to explicitly whitelist the public static IPs of the ARCXA coordinator/shard instances.

• Credential Governance: ARCXA requires a dedicated service account assigned to a custom role (e.g., ARCXA_MIGRATION_ROLE).

  Critical Dependency: This role must be granted IMPORTED PRIVILEGES on the SNOWFLAKE shared database and USAGE + SELECT on the target database's INFORMATION_SCHEMA.

Databricks

• How ARCXA Extracts Value: ARCXA targets the Unity Catalog system tables (system.information_schema). It extracts structural metadata, table lineages, volume declarations, and ACL permissions.

• Firewall & Network Scoping: Connection goes through Databricks SQL Warehouses or Clusters via JDBC/ODBC. If ARCXA is deployed on-premise (e.g., via a Dell XR7620 or IBM Power server), you must provision an Azure ExpressRoute, AWS Direct Connect, or secure VPN to bypass enterprise firewalls to hit the workspace VPC.

• Credential Governance: Requires a Databricks Personal Access Token (PAT) or an OAuth M2M (Machine-to-Machine) Service Principal.

  Critical Dependency: The Service Principal must have SELECT privileges on the system.information_schema catalog and BROWSE or SELECT on the catalog being analyzed.

2. Open-Source & Modern Relational Databases

PostgreSQL

• How ARCXA Extracts Value: ARCXA scrapes Postgres standard information_schema catalogs along with native internal system catalogs like pg_catalog.pg_proc (for stored procedures/functions), pg_trigger (for execution flows), and pg_inherits (for table partitioning).

• Firewall & Network Scoping: Postgres typically listens on port 5432. If the database sits behind an enterprise perimeter, firewalls must allow inbound traffic from ARCXA. Crucially, the target Postgres instance's pg_hba.conf file must be modified to allow the ARCXA IP to connect.

• Credential Governance: A dedicated user with CONNECT privileges to the database. To scrape system tables, the user must have read access on information_schema and pg_catalog. For deep stored-procedure reading, they may require SELECT on pg_proc or membership in the pg_read_all_stats default role.

MySQL

• How ARCXA Extracts Value: ARCXA crawls the INFORMATION_SCHEMA and the sys schema, specifically targeting ROUTINES (for stored procedures) and KEY_COLUMN_USAGE (for foreign key paths).

• Firewall & Network Scoping: Uses port 3306. Enterprise routing must allow ARCXA to cross subnet boundaries to hit the target.

• Credential Governance: Requires a user with explicit privileges:

  SQL

  GRANT SELECT, SHOW VIEW, TRIGGER on *.* TO 'arcxa_service'@'';
  

  Critical Dependency: Without SHOW VIEW and TRIGGER, ARCXA cannot read the logical business code inside views and trigger execution loops, blinding the KGNN algorithm.

3. Traditional Legacy Enterprise Engines

Microsoft SQL Server

• How ARCXA Extracts Value: ARCXA queries INFORMATION_SCHEMA alongside native system catalog views like sys.objects, sys.sql_modules (which exposes the raw T-SQL code of stored procedures), and sys.foreign_keys.

• Firewall & Network Scoping: Standard communication on port 1433. If SQL Server is tied to a local Active Directory domain, network routing must support the authentication handshake if Windows Auth is requested.

• Credential Governance: While SQL Server native authentication is simplest, enterprise governance often mandates Active Directory (AD / Entra ID) integration.

  Critical Dependency: The ARCXA service account must be granted the database-level role db_datareader on target databases, or explicitly granted VIEW DEFINITION at the database level so it can read the underlying T-SQL within stored procedures.

Oracle Database

• How ARCXA Extracts Value: ARCXA targets Oracle's powerful Data Dictionary views, primarily ALL_TAB_COLUMNS, ALL_CONSTRAINTS, and ALL_SOURCE (which stores the raw text of PL/SQL packages, procedures, and triggers).

• Firewall & Network Scoping: Runs over port 1521 (or custom listener port). Traffic must be allowed past local network appliances, and if Oracle Connection Manager (CMAN) is deployed, ARCXA must be added to the allowed routing rules.

• Credential Governance: Oracle database administrators are notoriously strict. ARCXA will need a dedicated schema-reading user account.

  Critical Dependency: The account must be explicitly granted the SELECT_CATALOG_ROLE system role or explicit SELECT privileges on sys.dba_source, sys.dba_constraints, and sys.dba_views. Without this, the KGNN platform cannot parse the underlying PL/SQL logic.

IBM Db2

• How ARCXA Extracts Value: ARCXA crawls the internal system catalog tables under the SYSCAT schema—specifically SYSCAT.TABLES, SYSCAT.REFERENCES, and SYSCAT.ROUTINES (to extract SQL PL stored procedures).

• Firewall & Network Scoping: Communicates typically on port 50000 (or 50001 for SSL). Because Db2 often runs on massive on-prem infrastructure (like IBM Power or Z Mainframes), firewalls protecting these core environments require extensive clearance forms.

• Credential Governance: The migration user must be granted database-level authority or systemic read privileges.

  Critical Dependency: The service account must possess DATAACCESS authority or explicit SELECT privilege on the SYSCAT schema views.

Phase-One Scoping Checklist for the Engagement Team

When running an initial scoping conversation with a client, use this clear hierarchy to lock down permissions before the engineers start work:

Cloud / modern (Snowflake, Databricks, SQL Server) — ArcXA reads the SQL and schema objects natively, maps them into the SPO triple store, and surfaces lineage and governance metadata. For Snowflake and Databricks specifically, this is a strong play for organizations running Migration as a Product (MaaP) — they're often the destination, not the source, so ArcXA provides the pre-migration intelligence that tells them what's actually coming over before it lands.

Open-source RDBMS (MySQL, PostgreSQL) — lighter on stored procedure complexity but still rich in schema relationships. ArcXA's MRA (Migration Readiness Assessment) handles these well, and the SPO layer becomes the semantic backbone for any AI/NLP interface you want to put on top of them — which is where KGNN feeds in.

Enterprise / legacy (Oracle, IBM DB2) — this is ArcXA's core domain. Oracle PL/SQL and DB2 SQL PL are dense with business logic buried in stored procedures, packages, and functions. ArcXA's SQL-to-SPO mapping phase is specifically built to surface that hidden logic before migration — the "understand before you move" differentiator against mechanical tools like Informatica or AWS Glue.

IBM DB2 + Power11 is particularly relevant given your existing positioning — ArcXA and KGNN on Power11 isn't just a migration story, it's a native intelligence and governance story for the IBM installed base that never leaves.

ARCXA platform approaches inter-system SQL migrations

Equitus.ai’s ArcXA platform takes a different approach to inter-system SQL migration than traditional ETL (Extract, Transform, Load) or schema-copying tools.

ArcXA is a mapping intelligence and semantic governance engine built on a graph-native architecture (born from handling highly siloed, complex systems-of-systems in the defense sector), it doesn’t just blindly copy tables from Source A to Target B. 

__________________________________________________________________________

ARCXA adds value across highly regulated industries in specific ways:

ArcXA mapping is the solution to migrating complexities between major enterprise SQL engines (such as moving from a legacy Oracle or IBM Db2 mainframe database into a modern managed cloud instance like Azure SQL or AWS Postgres), 

___________________________________________________________________________________

Industry Verticals - Focused Middle Layers

1. Banking and Financial Services

Pre-Mapping can fix broken relationship or unmapped schema which can lead to massive compliance audit or transaction failures. Assisting Financial institutions moving core ledger or compliance data between SQL databases facing strict regulatory scrutiny. 

• Semantic Traceability & Provenance: Instead of relying on a human developer's interpretation of legacy financial codes, ARCXA maps native SQL source fields directly to unified ontology terms. It builds a graph-native trace of exactly why a legacy ACC_BAL_PREV field maps to a modern target field, preserving full row-and-column data lineage.

• Audit-Ready Compliance: It provides a continuous, policy-driven verification engine. Regulators can physically see the workflow trail, schema evolution, and system-of-systems validation, guaranteeing that no data definitions shifted during transit.

2. Healthcare and Life Sciences

Clean up the  complex Migration of electronic health records (EHR) or clinical trial data between systems is notoriously messy because different legacy databases use conflicting data structures and naming conventions for identical medical concepts.

• Multi-Source Normalization: ARCXA uses model-assisted inference to dynamically suggest matches between highly disparate database schemas. For instance, if one database uses an old SQL Server schema for patient charts and the target uses a customized PostgreSQL instance, ARCXA's ontology-aware layer aligns both to a unified healthcare vocabulary (like HL7 or SNOMED standards).

• Validation Without Exposure: Because it can deploy completely on-premise or in private environments on secure servers, healthcare networks can manage complex schema mappings and validation dry-runs without sending sensitive patient data to third-party public clouds.

3. Supply Chain, Logistics, and Manufacturing

Reinvigorate - Global supply chains relying on ancient, highly complex ERP (Enterprise Resource Planning) databases built on IBM Db2 mainframes or Oracle. 

Pre-Migrating Mapping these to a modern, distributed cloud SQL architecture can break fragile downstream operational dependencies.

• Systems-of-Systems Interoperability Tracking: ARCXA maps out downstream dependencies before the cutover happens. It identifies which external shipping, inventory, or procurement systems rely on the specific SQL tables being shifted.

• Workflow Dry-Runs: Teams can execute dry-runs and validation schedules within ARCXA to test data integrity and latency behavior before executing the final migration script, preventing unexpected supply chain disruptions.

• 
  

4. Defense, Intelligence, and National Security

Equitus's foundational playground is defense. In this vertical, SQL migrations often involve moving highly classified operational data across isolated networks (Air-Gapped environments).

• Governed Edge Deployment: ARCXA is designed to run in highly secure environments without needing a persistent internet or cloud connection.

• Graph-Oriented Governance: It automatically structure structural discrepancies into a schema-less validation layer. If an operator is migrating tactical or intelligence databases, ARCXA ensures that entity relationships (e.g., identifying cross-border links or operational logistics) are preserved identically in the new target SQL architecture without data loss.

__________________________________________________________________________

Start a Migration Readiness Assessment, contact a Automation Engineer.

ArcXA:  Contact us at info@arcxa.com

ASC Ai cost/risk control

 

Data Governance Management for the AI Era

SIGNIFICANTLY REDUCE COST AND RISK OF MIGRATION

ArcXA SQL Consulting (ASC) Mapping automation modernizes legacy SQL data environments. Ingestion of data transforms into semantic intelligence, thru a unique triple-store architecture.  Triple Store Mapping protects critical business  dramatically reducing costs by accelerating analytics and AI readiness.   

ASC provides Free to Use / Open Source solutions.

________________________________________________________________

Problems ASC Solves: Migrating legacy SQL databases is traditionally slow, expensive, and risky. 

ASC eliminates the severe pain points that plague CTOs, COOs, and IT leadership:

• Skyrocketing Costs: We eliminate massive cloud egress fees and runaway GPU compute costs.

• Unpredictable Timelines: Automation replaces manual rewriting, keeping your migration strictly on schedule.

• Lost Schema Context: We preserve the institutional knowledge hidden inside your legacy systems.

• Data Lineage Breakage: We maintain a flawless, unbroken chain of data custody from source to target.

Improve your IT 

If your Company or Enterprise has stuck Ai projects or is planning a major SQL Migration we can Assist with an Automation Engineer :

1. The Elevators Pitch (For Sales & Networking)

"ASC systematically controls legacy SQL migrations. Instead of dealing with runaway GPU costs, broken data lineage, and unpredictable timelines, we use semantic intelligence and a triple-store architecture to protect your data's meaning while fast-tracking you for AI readiness."

 

Cost Category	Traditional Migration Cost	ASC Migration Cost	Total Savings
Manual Labor / Consulting	$3,500,000 (2 years)	$700,000 (~5 months)	$2,800,000
GPU / Compute Infrastructure	$450,000	$135,000	$315,000
Cloud Egress Fees	$250,000	$125,000	$125,000
Post-Migration Fixes & Downtime	$600,000 (Estimated)	$0 (Flawless lineage)	$600,000
Total Project Cost	$4,800,000	$960,000	$3,840,000

The Compelling Bottom Line: ASC delivers an 80% reduction in total migration costs while compressing the project timeline from years to months.

 

SIGNIFICANTLY REDUCE COST AND RISK OF MIGRATION

Executive leadership, Reduce cost improve Return on Investment:  Start you Migration Readiness Assessment and start saving.

• CFO (The Financial Case): "We shift your migration from a multi-year, unpredictable financial black hole into a fixed-cost, high-ROI initiative with an immediate payback period."

• CTO (The Opportunity Cost): "By automating the tedious rewriting process, your top-tier data engineers can spend their time building new revenue-generating features instead of manually translating legacy SQL."

• Chief Risk Officer (The Compliance Case): "Data lineage breakage isn't just annoying; it's a regulatory nightmare. ASC ensures a flawless chain of custody, eliminating audit risks entirely."

Role	Core Pain Point	ASC Solution
CTO	Lost schema context & broken lineage halting AI initiatives.	Semantic Intelligence preserves data relationships flawlessly.
COO	Unpredictable timelines delaying business operations.	Automation engine that ensures on-time, predictable delivery.
IT Director	Runaway GPU compute and massive cloud egress costs.	Optimized architecture designed to minimize infrastructure overhead.

___________________________________________________________________________________

Section 2 : Risk Reduction

ARCXA:  transforms risk mitigation from a manual, spreadsheet-driven guessing game into a deterministic, graph-verified truth. For AML and ICAM, this means zero post-migration downtime, zero regulatory fines, and absolute certainty during a federal audit.

Chief Risk Officer (CRO), monitoring data lineage is an IT asset and legal shield. When migrating legacy SQL databases using ARCXA (the engine powering ASC), its capability to provide graph-native semantic mapping and transformation traceability turns compliance from a reactive audit nightmare into a proactive defensive strategy.

 ARCXA's schema and field-level lineage mapping creates airtight, compelling use cases for Anti-Money Laundering (AML) and Identity, Credential, and Access Management (ICAM) perfect for users in highly regulated environments,

1: Anti-Money Laundering (AML) & Transaction Monitoring

AML compliance, a bank must prove to regulators (like FINMA or FinCEN) exactly how a suspicious transaction alert was generated. If a legacy SQL database migration breaks the historical schema or drops field context, the underlying AML models will ingest corrupt data, resulting in false negatives or unexplainable "black box" alerts.

ARCXA Solves AML:

• "Proof of Origin" Requirement: Regulators require a "defensible, auditable trail" showing that financial data used in AML scoring models matches the original source records. ARCXA maps source-native fields directly to standard compliance ontologies using unified multi-source normalization.

• Catching Layering and Smurfing: Money laundering relies on splitting and obscuring data paths. If a database migration breaks column-level lineage, historical records look disconnected. ARCXA uses graph-native provenance to ensure that across schemas, database shards, and platforms, the transactional chain of custody is unbroken.

• The Audit Payload: When an auditor asks, "Why did your system flag this specific account for FinCEN reporting?" ARCXA provides an automated graph visualization showing exactly which operational source table, SQL transformation, and ETL pipeline touched that specific data point.

2: Identity, Credential, and Access Management (ICAM)

ICAM and Identity Governance frameworks (aligned with NIST Zero Trust standards) dictate that an enterprise must enforce and audit who has access to what data, when, and why. During massive legacy system migrations, user permissions, security groups, and data-level access controls (RBAC/ABAC) are often lost or scrambled in translation.

ArcXA Solves It: Combine Person, Password and Purpose

• Preserving Attribute-Based Access Control (ABAC): Modern ICAM relies heavily on user and data attributes (e.g., clearance level, department, geographic location) to grant dynamic data access. ARCXA prevents data lineage breakage by explicitly mapping these critical security metadata tags from the legacy database directly to the target environment.

• Eliminating Entitlement Creep and Orphaned Accounts: When databases are migrated manually, old security tables and deprecated admin credentials often accidentally port over or lose their structural context, leaving hidden security backdoors. ARCXA tracks schema evolution and active policies, flagging stale, degraded, or unmapped identity structures before they go live.

• Systems-of-Systems Contract Enforcements: In an enterprise ICAM architecture, identity data is constantly federated across multiple internal and external systems. ARCXA introduces revision-aware contract governance. If a target system tries to modify or query identity attributes in a way that violates access policies, ARCXA blocks the validation gap and logs the evidence with cryptographic attestation.

CRO's Ultimate Dashboard

ArcXA mapping, a CRO can view a single compliance interface that unifies both technical transformation and regulatory reality:

ArcXA SQL Consulting (ASC) Mapping automation modernizes legacy SQL data environments. Ingested data transforms into semantic intelligence, through a unique triple-store architecture.  Triple Store Mapping protects critical business meaning while dramatically accelerating analytics and AI readiness.