-
· Security & governance · Choosing an approach
Before You Embed NL2SQL for Customers: Tenant Identity, Row Filters, and Licensing
Planning customer-facing NL2SQL? Bind tenant identity server-side, enforce row filters below the model, test every granted table, and settle licensing first.
-
· Fundamentals · Choosing an approach
Should an Assistant Answer from Database Rows or Documents?
Route assistant questions by the fact they need: rows for counts, documents for rules, both for combined ones, with the route and sources shown to the reader.
-
· Accuracy & validation · Choosing an approach
Schema Prompting vs. Schema Retrieval: Choosing an NL2SQL Context Strategy
Full-schema prompting or retrieved context? How to measure table recall, join closure and wrong joins before choosing an NL2SQL context strategy.
-
· Choosing an approach
Build vs. Adopt an NL2SQL Engine: Engineering Cost, Maintenance, and Licensing
How to estimate build vs. adopt for an NL2SQL engine: a shared acceptance contract, ownership table, effort model, change rehearsals and BSL 1.1 licensing.
-
· Choosing an approach
Text-to-SQL vs. Semantic Layers (dbt / MetricFlow / Cube): Do You Need Both for AI Analytics?
When a semantic layer should own your metrics, when text-to-SQL fills the gaps, what dbt import into NLQueries transfers, and why routing needs tests.
-
· Security & governance · Choosing an approach
SaaS vs. Private Cloud vs. Self-Hosted NL2SQL: Cost, Data Flow, and Licensing
Compare vendor-managed, private-cloud and self-hosted NL2SQL with a data-flow recipient matrix, a labelled cost worksheet and licensing gates.
-
· Choosing an approach
Choosing an LLM for text-to-SQL: Claude, GPT, DeepSeek and Bedrock
There is no single best LLM for SQL generation. How to choose Claude, GPT, DeepSeek or Bedrock for nlqueries-core 0.4, and what each choice changes.
No posts match your search. Search all posts