Question 1

Does TextQL support Redshift Serverless?

Accepted Answer

Yes. TextQL fully supports both Amazon Redshift Serverless and traditional provisioned clusters. The connection setup is nearly identical — just provide your Serverless workgroup endpoint instead of a cluster endpoint. Ana auto-discovers schemas and tables regardless of which Redshift deployment model you use.

Question 2

Can TextQL query Redshift Spectrum external tables?

Accepted Answer

Yes. TextQL discovers external schemas and tables exposed through Redshift Spectrum, allowing Ana to query data stored in S3 alongside your native Redshift tables. You can ask questions that seamlessly join internal and external tables — no need to specify which is which.

Question 3

How does TextQL handle Redshift concurrency limits?

Accepted Answer

TextQL respects your Redshift cluster's WLM concurrency settings and queue configuration. Queries are submitted through standard channels and follow your existing workload management rules. Ana also includes query timeout safeguards to prevent runaway queries from consuming cluster resources.

Question 4

Can I ask questions that combine Redshift and Snowflake data?

Accepted Answer

Yes. TextQL supports multi-warehouse queries out of the box. You can ask a single question that joins Redshift data with Snowflake, BigQuery, Postgres, or any other connected source. TextQL handles the federation, data transfer, and result merging behind the scenes.

Question 5

Does TextQL store any of my Redshift data?

Accepted Answer

No. TextQL operates as a query pass-through — all queries execute directly in your Redshift cluster, and results are streamed to your session without being persisted. TextQL stores only connection metadata and query history (which you control). Your data never leaves your AWS environment.