After a disaster, a client’s SQL Server setup failed the rule Reporting Services catalog database file existence. Here is why and how I got the install through.
ALTER Column From INT to BIGINT: Errors and Safe Solutions
To change a column from INT to BIGINT, you first drop every key and index that depends on it, because ALTER COLUMN refuses with Msg 5074 and Msg 4922. This post builds a small ticket system, shows the errors, and changes the key and its foreign key inside one transaction. It also shows how a negative identity reseed buys time, and when to copy the table instead.
SQL SERVER – Could Not Load File or Assembly ‘SqlManagerUi, Version=14.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91’ or One of its Dependencies
SSMS database properties failed with “Could not load file or assembly SqlManagerUi” for my client. Here is what caused the error and how we fixed it.
SQL SERVER – FIX: Msg 3009, Level 16 – Could not Insert a Backup or Restore History Detail Record in the msdb Database
A slow restore that my client cancelled led to Msg 3009: could not insert a backup or restore history record in msdb. Here is what I learned about a trace flag.
SQL SERVER – Error: Timeout (30000 milliseconds) Waiting for the SQL Server (MSSQLSERVER) Service to Connect
Timeout 30000 milliseconds waiting for the SQL Server service to connect. Why the service start times out, what to check, and how to give it longer.
Msg 3168: Backup Made by a Different SQL Server Version
Msg 3168 stopped a client from restoring master after a ransomware attack, because the backup and the new server had different build numbers. The fix is to make the two builds match, by patching up or uninstalling patches, and then restore again.
SQL SERVER – Unable to Restore from URL – The Specified URL Points to a Block Blob. Backup and Restore Operations on Block Blobs are not Permitted
Restore from URL failed: operations on block blobs are not permitted. Checked against today’s documentation, the credential decides the blob type.