how-to-subset-create2

Database subsetting is complex due to several challenges:

When selecting a subset of rows from a table, you must also get the rows of related tables.
A relational constraint may be on multiple columns (Composite keys). In this case a subset requires rows of related tables using the multiple column constraint.
Some tables may have no foreign key columns but may have other tables that have foreign keys referencing the table.
Cyclical dependencies. Table A has a foreign key to table B and table B has a foreign key back to table A.

LangGrant solves these challenges with a simple visual interface. Start by specifying a percent of the source database size, with or without bias controls. Windocks subsetting does not write to the source database (the one being subsetted).

Let's Meet

Orchestration: automated database context

LEDGE automatically delivers complete database context for LLMs to comprehend multiple databases simultaneously at scale. Like a skilled engineer, once an LLM understands databases it can contribute to solution design.

Orchestration: analytic plan

LEDGE binds LLMs to deliver accurate analytic plans for user queries. Plans are saved, easily validated and modified, and run to deliver analytics data within minutes of the user query.

Governance

PII safeguards, authorization controls, data residency rules, firewall restrictions, and token-governance policies are built-in by design. No sensitive data leaves governed systems.