To connect TextQL with your Snowflake instance, you will need to gather the following connection details:
  • Account identifier (your Snowflake locator)
  • Database name and Schema
  • Warehouse name (optional)
  • Authentication credentials (username/password or JWT private key)
  • Role name (optional)

​
Creating the Connector in TextQL

Navigate to the TextQL Connectors Page and click Create New Connector. Select Snowflake from the available connectors to open the configuration form. The form requires the following information:
  • Connector Name: A descriptive name to identify this specific Snowflake connection in TextQL.
  • Account Identifier: Your Snowflake account locator (e.g., xy12345.us-east-1).
  • Database: The name of your target Snowflake database.
  • Schema: The schema name within your database (optional).
  • Warehouse: The compute warehouse to use for queries (optional).
  • Role: The Snowflake role to assume for this connection (optional).

​
Authentication Methods

TextQL supports two authentication methods for Snowflake:
  1. Username and Password:
    • Username: Your Snowflake username
    • Password: Your Snowflake password
  2. JWT Authentication:
    • Username: Your Snowflake username
    • Private Key: Your JWT private key for authentication
Select your preferred authentication method in the form. For JWT authentication, ensure your private key is properly formatted and the corresponding public key is registered in your Snowflake account.

​
Testing the Connection

After entering your credentials, click Create to establish the connection. TextQL will validate your credentials and create the connector. If the connection fails, verify your account identifier and authentication details.

​
Next Steps

Once connected, you can use TextQL to query your Snowflake data. The connector automatically handles session management and warehouse resumption. For optimal performance:
  • Configure an appropriate warehouse size for your workload
  • Set up a dedicated role with appropriate privileges
  • Use schema specification to limit data access scope