Query Runner Connection Overrides

Help ID: query-runner.connections

The Query Runner connection manager stores repository-backed credentials used for ad hoc and saved-query execution in repo mode.

[Image omitted: Query Runner connection overrides]

Walkthrough

Open Query Runner.
Open the Options target tab.
Click Connections.
Select Global default to edit the default connection used by every server without an override.
Select a server scope to set or change the connection for that specific server.
Pick Windows or SqlLogin.
Set command timeout and certificate trust behavior.
Keep Active checked for credentials that should participate in resolution.
Click Save.

Repo Mode Resolution Rules

Saved credentials are resolved per server. A server-specific active row wins over the global row. The global row uses InstanceID = 0. If neither saved credential exists, the run falls back to the current query-runner authentication settings.

Passwords are encrypted before being stored in the repository. The target list shows the resolved user beside each server so operators can catch the wrong login before they run the query.

Standalone Mode

Standalone mode uses local JSON target profiles instead of repository connection overrides. Those profiles are stored in QueryRunnerTargets.json, and SQL login passwords are encrypted with the same Encryption.Secrets path used here.

The connection manager remains the repo-mode credential editor. A standalone target editor can sit on top of the JSON store without changing how repo credentials are resolved.