ItTiger.TigerSqlCmd 0.8.9

TigerSqlCmd

tiger-sqlcmd is a modern SQL Server CLI built on TigerQuery for SQL script execution, saved connection profiles, interactive and non-interactive automation, CI and agent workflows, and safe session-scoped E2E database lifecycles. It combines TigerQuery's SQLCMD-compatible parser and execution engine with connection management, output routing, stable exit codes, and external-tool integration.

Installation

Windows with WinGet

winget install ItTiger.TigerSqlCmd

WinGet installs TigerSqlCmd machine-wide and resolves its .NET 10 runtime dependency. The package is published in the Windows Package Manager community repository as ItTiger.TigerSqlCmd.

.NET tool

dotnet tool install --global ItTiger.TigerSqlCmd

Use a .NET 10 SDK to install the .NET tool. Older SDKs can misleadingly report that DotnetToolSettings.xml is missing even though the package contains it; check dotnet --version and any applicable global.json if that happens.

Shell completion

tiger-sqlcmd --completion bash|zsh|fish|pwsh prints a tab-completion script to activate in your shell, for example in PowerShell:

tiger-sqlcmd --completion pwsh | Out-String | Invoke-Expression

See Shell completion for persistent activation in each shell.

Quick start

tiger-sqlcmd connection list
tiger-sqlcmd connection add local --server sql01 --database AppDb --non-interactive
tiger-sqlcmd run --connection local --query "SELECT DB_NAME();" --non-interactive
tiger-sqlcmd run --connection local --file deploy.sql --non-interactive

The command group is connection (singular). Saved profiles can use integrated or SQL authentication and can resolve sensitive or environment-specific values from supported external references instead of storing them directly.

One Command Model, Multiple Interaction Modes

Normal execution is semi-interactive and can prompt for eligible missing input. Add --non-interactive to the same command for scripts, CI jobs, scheduled work, and agents. Command semantics and safety checks stay the same; missing promptable values fail clearly instead of blocking.

See TigerSqlCmd interaction modes and general usage.

E2E workflows

tiger-sqlcmd e2e create --session-id 11111111-2222-3333-4444-555555555555 --name-part smoke --non-interactive
tiger-sqlcmd run --connection E2E-smoke-<generated-suffix> --file tests.sql --non-interactive
tiger-sqlcmd e2e cleanup --session-id 11111111-2222-3333-4444-555555555555 --non-interactive

An owned E2E database and its saved connection are correlated to the session, and cleanup applies exact ownership and authorization checks. A connection clone-e2e profile for a pre-existing database is non-owning, so cleanup removes only the saved connection and never drops that database. Add --memory-optimized to e2e create when the database must host memory-optimized tables.

See the complete TigerSqlCmd E2E guide.

External tools

tiger-sqlcmd exec --connection local --connection-string-env DB_CONNECTION -- my-tool --report

exec resolves the saved connection and passes it to one external process through the supported environment-variable and/or {connection-string} argument handoff. Every TigerSqlCmd option goes before the raw -- separator; everything after it is the child command line.

See Running an external tool: exec.

Documentation

• TigerSqlCmd general guide
• TigerSqlCmd E2E guide
• TigerQuery documentation home
• TigerQuery repository

License, third-party software, and privacy

TigerSqlCmd is licensed under the MIT License; the package carries it as LICENSE. It also includes third-party components under their own licences, listed and reproduced in the package's THIRD-PARTY-NOTICES.md. One of them, Microsoft.Data.SqlClient.SNI.runtime, is licensed by Microsoft under the Microsoft Software License Terms, not under the MIT License. Each release attaches the privacy statement, PRIVACY.md, that applies to that version.