Fivetran
Fivetran documentation
Search the docs
/
Sign In
  • Getting Started
  • Core Concepts
  • Connectors
    • Applications
    • Databases
      • Connection Options
      • HVA Connectors
      • Amazon DocumentDB
      • Amazon DynamoDB
      • Azure Cosmos DB
      • BigQuery
      • CockroachDB
      • Convex
      • Databricks
      • Db2 for i
      • Db2 for LUW
      • Db2 for z/OS
      • Elasticsearch
      • Epic Clarity
      • Firebase
      • MariaDB
      • MongoDB
      • MySQL
        • Setup Guide - Generic MySQL
        • Setup Guide - Amazon Aurora MySQL
        • Setup Guide - Azure Database for MySQL
        • Setup Guide - Google Cloud SQL for MySQL
        • Setup Guide - RDS MySQL
        • Troubleshooting
          • Add Read Timeout
        • Release Notes
      • OpenSearch
      • Oracle
      • PlanetScale
      • PostgreSQL
      • SAP
      • SingleStore
      • Snowflake
      • SQL Server
      • Troubleshooting
    • Events
    • Files
    • Functions
    • AI Connector Agent
    • By Request
    • Partner-Built
    • Troubleshooting
  • Connector SDK
  • Destinations
  • Managed Data Lake Service
  • Context Layer
  • Transformations
  • Activations
  • Logs
  • Security & Privacy
  • REST API
  • HVR 6 Documentation
  • Release Notes

What Read Timeout Value Should I Set for Queries on My MySQL Instance?

Question

What read timeout value should I set for queries on my MySQL instance?

Environment

Connector: MySQL

Answer

Here are a few things that can impact query performance:

  • The volume of data
  • Network Latency
  • Size of the environment

We recommend that you set any timeout parameter to 1 hour for our queries to complete without interruption, and increase that parameter by an additional hour if needed.

Thanks for your feedback!
Was this page helpful?
On this page
Loading...
More from Fivetran
Fivetran status
Contact us
Need help?
Contact support
Sign inCreate an account
BlogCase studiesResource center
Fivetran
©2026 Fivetran Inc.