Question 1

Can TextQL query across multiple Snowflake databases in one question?

Accepted Answer

Yes. TextQL's Ana agent can join data across multiple Snowflake databases and schemas in a single natural language query. It automatically resolves cross-database references and generates the correct fully-qualified table names, so you can ask questions that span your entire Snowflake account without writing any SQL.

Question 2

Does TextQL respect my Snowflake role-based access controls?

Accepted Answer

Absolutely. TextQL connects using the Snowflake role you assign, inheriting all its permissions and restrictions. Ana can only access the tables and columns that role is granted. Your existing RBAC policies, row-level security, and data masking rules are fully enforced — TextQL never bypasses Snowflake's security model.

Question 3

How does TextQL handle large result sets from Snowflake?

Accepted Answer

TextQL streams results and intelligently summarizes large datasets so you get actionable answers without downloading millions of rows. For detailed exploration, Ana can paginate results, apply top-N filters, or aggregate on the fly. You can also export full result sets to CSV or send them to downstream tools.

Question 4

Can I use TextQL alongside my existing dbt models?

Accepted Answer

Yes. TextQL auto-discovers dbt models materialized in Snowflake as tables or views. It reads your schema metadata — including column descriptions if available — to generate more accurate queries. You don't need to reconfigure anything; Ana simply queries whatever dbt has already built in your warehouse.

Question 5

What happens if Ana writes an inefficient query?

Accepted Answer

TextQL includes built-in query guardrails that estimate cost and scan size before execution. If a query would scan an unusually large amount of data, Ana flags it and suggests an optimized alternative. You can also set warehouse-level cost limits and timeout thresholds directly in your TextQL workspace settings.