Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Jan 31, 2026

On Linux, sqlcmd with -t flag correctly prints "Timeout expired" but hangs for ~10 minutes before exiting. Works correctly on Windows.

Root Cause

runQuery() never closes the sql.Rows object returned by QueryContext(). On timeout, the connection remains open. Linux TCP stack waits ~10 minutes for cleanup; Windows cleans up more aggressively.

Changes

Added missing defer rows.Close() immediately after QueryContext():

rows, qe := s.db.QueryContext(ctx, query, retmsg)
if rows != nil {
    defer rows.Close()
}

This releases the connection immediately when the function returns, regardless of error or timeout conditions.

Original prompt

This section details on the original issue you should resolve

<issue_title>sqlcmd does not handle/honor the command timeout (-t) flag properly on Linux</issue_title>
<issue_description>sqlcmd does not properly handle/honor the SQL Command Timeout (-t) flag properly on Linux. It works fine on Windows but the command always "hangs" for ~10 minutes before finally exiting when run on a Linux system .

Testing Setup

Test Table

USE [dba]
GO

CREATE TABLE [dbo].[DBScriptTable](
	[id] [bigint] IDENTITY(1,1) NOT NULL,
	[placeName] [varchar](100) NULL,
    PRIMARY KEY CLUSTERED ([id] ASC) 
) ON [PRIMARY]
GO

Blocker DML

This script will create an open transaction against the above table with SERIALIZABLE transaction isolation level. Running it without completing the transaction will essentially block all operations on the table until the script is either rolled back or committed. That's why the ROLLBACK is commented out here.

-- This should be run from within SSMS so you can control the transaction
SET TRANSACTION ISOLATION LEVEL SERIALIZABLE ;

BEGIN TRANSACTION

INSERT INTO DBscriptTable (placeName) VALUES ('Redmond, Washington') ;

--ROLLBACK TRANSACTION

Test DML

Simple select to use for our sqlcmd tests

-- Save as test.sql
SELECT * FROM DBScriptTable
GO

How to replicate this behavior

  1. Create the test table in a database named dba

  2. Run the Blocker DML with the ROLLBACK commented out from SSMS. This will block all operations on the table. Using something like sp_WhoIsActive you should be able to verify that we now have a sleeping session with an open transaction for this.

  3. Run sqlcmd script below in PowerShell on Windows 11. You will notice that this script will return immediately after the command timeout of 1 second

PS> get-date; sqlcmd -S "<redacted>" -U "<redacted>" -P "<redacted>" -i ./test.sql -d dba -t 1; get-date

Tuesday, August 12, 2025 10:20:26 AM
Timeout expired
Tuesday, August 12, 2025 10:20:27 AM

PS>
  1. Run the sqlcmd script below on a Linux system in bash. You will notice that the SQL "Timeout expired" message will appear after 1 second, but sqlcmd does not return us to a bash prompt for 10 minutes. I'm not exactly sure what it's waiting on here and this is the unexpected behavior.
$ date; sqlcmd -S "<redacted>" -U "<redacted>" -P "<redacted>" -i ./test.sql -d dba -t 1; date

Tue Aug 12 10:19:56 EDT 2025
Timeout expired
Tue Aug 12 10:29:57 EDT 2025

$
  1. Make sure you uncomment and execute the ROLLBACK in the SQL script to complete that transaction.</issue_description>

Comments on the Issue (you are @copilot in this section)


💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

Co-authored-by: dlevy-msft-sql <194277063+dlevy-msft-sql@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix sqlcmd command timeout handling on Linux Fix sqlcmd hanging for ~10 minutes after query timeout on Linux Jan 31, 2026
Copilot AI requested a review from dlevy-msft-sql January 31, 2026 19:55
@dlevy-msft-sql dlevy-msft-sql added bug Something isn't working Size: S Small issue (less than one week effort) connectivity needs-work labels Feb 1, 2026
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR fixes a critical bug where sqlcmd hangs for approximately 10 minutes after a query timeout on Linux systems. The root cause was a missing rows.Close() call in the runQuery() function, which left database connections open and caused the TCP stack on Linux to wait for cleanup. The fix adds the standard Go pattern of defer rows.Close() immediately after QueryContext() to ensure connections are properly released.

Changes:

  • Added defer rows.Close() call with nil check in runQuery() function to properly release database connections when the function returns

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working connectivity needs-work Size: S Small issue (less than one week effort)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

sqlcmd does not handle/honor the command timeout (-t) flag properly on Linux

2 participants