Fix SQL Server Execution Timeout Error - Skyvia

SQL Server: Execution Timeout Expired

Overview

The error Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding occurs when a SQL Server command takes longer to execute than the configured timeout limit allows. This is common when processing large datasets, running complex queries, or when the server is under heavy load.

Root Causes

  • The query or operation takes longer than the Command Timeout value configured in the Skyvia connection.
  • The server is slow to respond due to high load or resource constraints.
  • Network latency between Skyvia and the SQL Server instance.
  • Missing indexes on the queried table causing full table scans.

Resolution

Step 1: Increase timeout values in Skyvia

  1. Go to Skyvia → Connections.
  2. Find and open your SQL Server connection.
  3. Click Edit.
  4. Scroll down and open Advanced Settings.
  5. Increase the following values:
    • Command Timeout — maximum time (in seconds) allowed for a single command to execute. Set to 5000 or 0 for no limit.
    • Connection Timeout — maximum time (in seconds) to wait when establishing a connection. Set to 5000 or 0 for no limit.
  6. Click Save and retry the integration.

Step 2: Check timeout settings on the SQL Server side

If increasing Skyvia timeout values does not resolve the issue, review and adjust timeout settings on the SQL Server instance itself. Remote query timeout can be configured via:

EXEC sp_configure 'remote query timeout', 0;
RECONFIGURE;

Setting the value to 0 disables the timeout on the server side.

Step 3: Optimize the query or integration

  • Add indexes to columns used in filters or joins.
  • Reduce the number of records processed per run using filters in the integration.
  • Enable Incremental mode if available for the integration type to process only new or changed records.

Useful Links

    • Related Articles

    • MySQL: Lost connection to MySQL server during query

      Overview The error Lost connection to MySQL server during query occurs when the connection between Skyvia and the MySQL server is dropped while a command is being executed. This typically happens when processing large datasets or when server-side ...

    • Query execution timeout exceeded error

      Overview This error occurs when a query takes too long to execute, typically because it processes a large dataset or uses inefficient filters. Resolution Apply WHERE filters to reduce the amount of data being queried. Review and optimize JOINs and ...

    • UPDATED: Salesforce: Expired access/refresh token

      Overview If you see an "expired access/refresh token" error, your Salesforce OAuth connection is invalid. This happens when the token has expired, been revoked, or invalidated by a Salesforce security policy change. Possible Causes The OAuth token ...

    • Skyvia Query: Verify Data in Your Connection

      Overview Skyvia Query allows you to browse and verify data in any connected data source directly from the Skyvia interface, without writing complex scripts or using third-party tools. You can use the visual Builder view or write custom SQL ...

    • PostgreSQL: A call to SSPI failed, see internal exception

      Overview The error "A call to SSPI failed, see internal exception" indicates that the security protocol (SSL/TLS) used in your PostgreSQL connector does not match the version supported by your server. Resolution Try different SSL/TLS protocol ...