AUTOMATIC SQL DELIVERY
Install a small sync agent once beside your database. It checks TermHub for new published releases on a schedule and copies the sources your organisation is entitled to use. No recurring commands, downloads or manual release selection.
1 · Destination
Connect DBeaver, TablePlus, Azure Data Studio or your existing tool to PostgreSQL, MySQL or Microsoft SQL Server that you control.
Create a least-privileged database user that can create and update only termhub_* tables.
2 · Install once
The agent runs continuously in your environment and restarts after a reboot. TermHub never receives your database password or opens an inbound connection to your network.
3 · Automatic updates
Each cycle reads the release manifest, discovers every entitled published source and updates the matching tables. Set the default interval to hourly, or choose 5 minutes to 24 hours.
There is no separate action for a newly added code system.
Data-team layer
Alongside the canonical release-history tables, the agent creates one current table pair per entitled source. dm+d also receives familiar VTM, VMP, AMP, VMPP and AMPP views.
These current objects refresh automatically; historical work remains in the canonical termhub_concepts and termhub_relationships tables.
Access control
Every scheduled check validates your subscription and source access. If payment fails, a trial expires or access is suspended, the next sync is refused immediately.
The agent remains installed and resumes automatically when access is restored. Existing copied data remains subject to the applicable licence terms.
mkdir termhub-sql && cd termhub-sql
curl -O https://www.termhub.co.uk/sql/termhub-sync.mjs
curl -O https://www.termhub.co.uk/sql/package.json
curl -O https://www.termhub.co.uk/sql/Dockerfile
curl -O https://www.termhub.co.uk/sql/docker-compose.yml
curl -O https://www.termhub.co.uk/sql/termhub-sql.env.example
cp termhub-sql.env.example .env
# Add your saved API secret and database URL to .env
docker compose up -d --buildUse the API secret from API, not the Key ID. Keep it in the local termhub-sql.env file or your secret manager; never paste it into a SQL UI, browser app or source control. For a database running on your Mac, use host.docker.internal in the connection URL, not localhost.
After a successful sync, refresh your SQL UI. The agent creates:
termhub_releases — source and checksum provenancetermhub_current_releases — current release per sourcetermhub_concepts — terminology conceptstermhub_relationships — hierarchy and mapping datatermhub_sync_runs — local sync audit trailSELECT c.code_system, c.code, c.display, c.active
FROM termhub_concepts c
JOIN termhub_current_releases current_release
ON current_release.release_id = c.release_id
WHERE c.display ILIKE '%paracetamol%'
LIMIT 50;