✨ Yardi SQL Query Assistant · Included in every PROPETL tier

Ask Your Yardi Database Anything.

A queryable knowledge base of the entire Voyager schema — inside Claude. Find the right tables, discover join paths, decode the magic numbers, and draft execution-verified ySQL in seconds instead of afternoons.

Try Free — 24 Hours, No Card →See it in action
✓ 9,793 tables · 137,000+ columns✓ Join-path discovery over 12,900+ relationships✓ 33 execution-verified ySQL patterns✓ Enum decodes for the codes nobody documents

9,793

Voyager Tables Indexed

137,000+

Columns Catalogued

12,900+

Table Relationships

33

Verified ySQL Patterns

The Problem

The data is in there. Finding it is the job nobody budgets for.

If you write queries or reports against Voyager, you know these moments.

Ten thousand tables, zero documentation

Voyager's schema is enormous and the naming is tribal knowledge. Is it TENANT, CTENANT, or a row in a polymorphic table? You grep table names and hope, because nobody documented which of the 9,793 tables actually holds what you need.

Join paths are guesswork

You know the data is in TRANS and you know the property is in PROPERTY — but the join goes through columns whose names give nothing away. One wrong hop and your revenue report double-counts every reversal.

Magic numbers everywhere

iType = 7. iStatus = 2. sType = 'K'. Voyager stores meaning as integer codes that only decode correctly if you already know the answer. Getting one enum wrong silently corrupts every downstream report.

How It Works

Ask in plain English. Get tables, join paths, and draft ySQL.

Part of the PROPETL Claude connector — same one-time setup, no extra install.

Claude.ai — PROPETL connector active
Which tables hold commercial lease charges, and how do I join them to the property?
📚 Found it. Posted lease charges live in TRANS (iType = 7 = Charge), with charge codes in CHARGTBL.
🔗 Join path: TRANS.hProp → PROPERTY.hMy, charge code via TRANS.hChargeCode → CHARGTBL.hMy.
⚠️ Heads-up: filter reversals via iStatus, and don't join through audit-history edges — they double-count.
Draft the query for all charges on property AR01 this year.
✅ Drafted from a verified pattern:
SELECT p.sCode, t.cAmount, t.dtDate,
       ct.sName AS ChargeCode
FROM   TRANS t
JOIN   PROPERTY p  ON p.hMy = t.hProp
JOIN   CHARGTBL ct ON ct.hMy = t.hChargeCode
WHERE  p.sCode = 'AR01'
  AND  t.iType = 7  -- Charge
  AND  t.dtDate >= '2026-01-01'
Run it in your usual ySQL surface — want a rent-roll version too?

Features

The schema knowledge of a 20-year Yardi admin. On tap.

Every answer grounded in an indexed schema knowledge base — not model guesswork.

Schema Search

Ask in plain English — "which tables hold commercial lease charges?" — and get the actual tables, their columns, data types, keys, and descriptions from a knowledge base of 9,793 standard Voyager tables.

Join-Path Discovery

Give it two tables and it finds the foreign-key route between them — walking 12,900+ inferred and confirmed relationships, and steering around audit-trail edges that produce wrong joins.

Verified ySQL Query Patterns

Execution-verified query templates for common asks — rent rolls, aged receivables, charge schedules, GL activity — with placeholders you fill in. Every pattern has been run against a live database before it ships.

Enum Decodes

The integer codes Voyager never explains, decoded: the complete 14-code TRANS.iType map, tenant status, ObjectType registry, book codes, and more — 228 install-invariant decode rows across 32 decoders.

Naming-Grammar Conventions

The H-prefix key grammar, polymorphic hRecord/hCode foreign keys, the HMYPERSON subtype trap, core spine joins — the curated conventions that separate a correct query from a plausible-looking wrong one.

Report-Writing Knowledge

Beyond ad-hoc queries: YSR and SSRS custom-report authoring knowledge — script format, //Columns and //Filter grammars, #token# substitution, render engines — plus full sanitized report skeletons by category.

Your Own Schema, Indexed

Your own schema can be indexed alongside the standard one — custom tables, views, and stored procedures in a private overlay, isolated from every other client. Available as a custom enhancement; email support@propetl.com.

Works Where You Already Work

It's part of the PROPETL Claude connector — no new app, no VPN into the database server. Ask questions mid-conversation while you're building imports, reports, or reconciliations.

Draft, Then Verify

The assistant drafts queries grounded in real schema facts and tells you what to verify — it never pretends to run SQL against your production database. You stay in control of execution.

Pricing

Included in every PROPETL tier.

The SQL Query Assistant ships with every tier — Free Trial, Solo Lifetime, and Team Lifetime — at no add-on fee. Indexing your own custom schema alongside the standard one is available as a separate enhancement.

Free Trial · Limited Time

$0

24-Hour Full Access · No card required

  • ✓ All 306 ETL modules — no limits
  • ✓ Auto-detect Yardi import type
  • ✓ Column mapping — 4 source systems (Yardi, MRI, CTI, JDE)
  • ✓ 5,204 cross-module validation rules
  • ✓ Clean ETL file download
  • ✓ Draft & generate ySQL queries on Yardi schema
  • ✓ No credit card required
Start Free Trial

License key issued instantly in your dashboard

MOST POPULAR

Solo Lifetime · 75% Off · Limited Time

$98 $388

One-Time Payment · Save $290

  • ✓ Everything in Free Trial
  • ✓ 1 license seat
  • ✓ Permanent connector access
  • ✓ 12 months automatic upgrades
  • ✓ New modules as released
  • ✓ Draft & generate ySQL queries on Yardi schema
  • ✓ Email support included
  • ✓ Active in under 5 minutes
Get Solo Lifetime — $98 (75% off)

Instant access. No subscription. No renewal.

Team Lifetime · 5 Seats · 80% Off

$388 $1,940

One-Time Payment · 5 Seats · Save $1,552 · $77.60 per seat

  • ✓ Everything in Solo — Lifetime
  • ✓ 5 lifetime license seats
  • ✓ Invite and reassign teammates from your dashboard
  • ✓ Seats revocable at any time
  • ✓ Issued on one verified company domain
  • ✓ Priority email support
  • ✓ Active in under 5 minutes
Get Team Lifetime — $388 (5 seats)

Seats are issued on your company email domain. Bought with a personal address (gmail, outlook, …)? Verify a work address first — it takes one click.

FAQ

Questions before the first query.

▸What exactly does the SQL Query Assistant know?

It carries a knowledge base of the standard Yardi Voyager 7S schema: 9,793 tables, 137,000+ columns with types and key flags, and 12,900+ inferred and confirmed foreign-key relationships. On top of the raw schema sit curated conventions — naming grammar, polymorphic foreign keys, core spine joins, enum decodes — and 33 execution-verified ySQL query patterns.

▸Does it connect to my Yardi database?

No. The assistant helps you find tables, discover join paths, and draft correct ySQL — it never connects to or executes anything against your database. You run the queries yourself through your normal tools. Indexing your own schema (custom tables, views, stored procedures) into a private overlay is available as a custom enhancement — email support@propetl.com.

▸Is this included in my PropETL license?

Yes. Schema querying ships with every tier — Free Trial, Solo Lifetime, and Team Lifetime. Fair-use quotas apply; they are set far above any realistic query-drafting workload.

▸What is ySQL?

ySQL is Yardi's SQL dialect and query surface for Voyager. The assistant's query patterns respect its constraints, so drafts are written to run where Voyager admins actually run queries.

▸Can it help me write Yardi custom reports?

Yes — alongside schema querying it carries a report-writing knowledge base: the YSR/SSRS script format, //Columns and //Filter grammars, #token# substitution, render engines including Word and Excel FillDocs templates, and full sanitized report skeletons by category.

Stop reverse-engineering the schema at 2am.

Try Free — 24 Hours, No Card →See all plans

Included in every tier · No extra setup beyond the connector

Questions? Book a discovery call