Connections by protocol tell you whether a client reaches SQL Server through shared memory, TCP or a named pipe, and from which address. This post reads the connection view for your own session, connects three ways to see each protocol, lists every connection with its host and program, and counts them by protocol.
Connection Strings Explained: Encrypt, TrustServerCertificate and Timeouts
Explain TrustServerCertificate, encryption modes, connection and command timeouts, listener failover, and server-side connection evidence.
Connection Timeout Expired: Log Shipping Job Failed to Connect to Server
Connection timeout expired failed a log shipping restore job at a client. The pre-login handshake alone took about 33 seconds, past the 30 second default. Staggering the jobs and adding -logintimeout 60 to the job step fixed it.
SQL SERVER – Unable to Start SQL Server Service or Connect After Incorrectly Setting Max Server Memory to a Low Value
After incorrectly setting max server memory to 14 MB instead of 145000, a client could not start SQL Server. Here is how we got it back online.
Listing Driver, Encryption and Auth Scheme for Every Connection
Inspect the auth scheme, encryption, driver interface, and protocol for current SQL Server connections, then group the results clearly.
Network-Related or Instance-Specific Error During SQL Server Installation
The network-related or instance-specific error is a wrapper message, and during a SQL Server 2014 RTM installation its cause was TLS compatibility. The tests here show how the same message appears for different failures, how to read the number inside it and how to check protocols and encryption.
Fix Error 3637: Backup Fails on a DAC Connection
To fix error 3637, find out why your backup runs on a dedicated administrator connection. This post reproduces the message with sqlcmd and its -A switch, shows the same backup working on a normal connection, and lists where a DAC hides in scripts and scheduled tasks.