A login event is a connection, not a user action. A small session shows how one query can leave three of them behind.
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.
Countdowns in T-SQL: Days, Hours and Minutes Until an Event
A countdown that says 1 day for a one-second gap is counting boundaries, not time. Here is how to build one that tells the truth.
Get-AzureStorageBlob: The Remote Server Returned an Error: (403) Forbidden. HTTP Status Code: 403 – HTTP Error Message: This Request is Not Authorized to Perform This Operation
A runbook cleaning old backup blobs in Azure failed with (403) Forbidden: This request is not authorized to perform this operation. Here is the fix.
SQL SERVER – Identify the column(s) responsible for “String or binary data would be truncated.”
For years, String or binary data would be truncated never told us which column was too long. Now SQL Server does, and here is how to identify the column responsible.
SQL SERVER – Script Level Upgrade for Database ‘master’ Failed Because Upgrade Step ‘SSIS_hotfix_install.sql’ Encountered Error 15151
Another SQL Server upgrade failure: upgrade step SSIS_hotfix_install.sql hit error 15151 because a user did not exist. Here is how I fixed it.
SQL SERVER – Error in Validation: Listener in Workgroup – Unable to determine if the computer exists in the domain ‘WORKGROUP’
A client’s domain-less Always On cluster in Azure could not create a listener: Unable to determine if the computer exists in the domain ‘WORKGROUP’. Here is why.