-
· 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.
-
· Security & governance · Build & integrate
Designing an Internal Slack Data Assistant with NLQueries: The Controls to Test First
Design notes for a Slack slash command on NLQueries Core: verify requests, map users to restricted database roles, recheck access at delivery, test first.
-
· Security & governance · Build & integrate
An NLQueries MCP Server Setup Checklist: Tools, SQL Checks and Authorization
A source-reviewed checklist for the NLQueries MCP server: stdio vs. SSE, its nine tools, grants per identity, and the denial tests to run before sharing it.
-
· 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.
-
· Security & governance · Databases
Natural-language BigQuery without service account keys: workload identity federation and impersonation
Query BigQuery in plain English with no service account key on disk, using workload identity federation, ADC and per-connector impersonation.
-
· Security & governance · Databases
Letting an LLM query production safely: read-only roles, statement policy and timeouts
LLM database security is defence in depth: a read-only identity, a SQL statement policy, timeouts and result caps, and an authenticated MCP server.
-
· Accuracy & validation · Security & governance
Why we validate SQL before it runs
The difference between a query that parses, a query that executes, and a query that answers the question. Three separate checks, and only one of them is free.
No posts match your search. Search all posts