What does BACKUP WITH NAME do? It simply names your backup, and you can then find that name in the msdb backupset table. Here is a quick example.
SQL SERVER – The Patch Installer has Failed to Update the Shared Features
Under a tight downtime window, a client got “The patch installer has failed to update the shared features”. Here is what the logs showed and how we fixed it.
How to Get Column Names From a Table in SQL Server
To get column names from a table in SQL Server, query sys.columns with OBJECT_ID, or read INFORMATION_SCHEMA.COLUMNS. This tutorial tests four methods on a demo table, shows the schema trap that returns too many columns, and builds a paste-ready column list. It also finds every table that has a given column.
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.
How Default Value and Nullable Column Works? – Interview Question of the Week #129
How do a default value and a Nullable Column work together in one table? Two short scripts from an interview panel show exactly what SQL Server does.
MSDB Growth From queue_messages: How to Clear the Queue
MSDB growth from the queue_messages tables means a Service Broker queue holds messages that nobody reads. This post builds a queue with unread messages in a test database, finds it with a size query, ends only its conversations with the CLEANUP option, and watches the space come back. It also says why you should never end every conversation in msdb.