Add Failover Cluster Node failed: this SQL Server edition does not support the installed number of cluster nodes. What Detail.txt showed and how to fix it.
SQL SERVER – Unable to See Tables (Objects) in SSMS
A client could query a table but was unable to see tables in SSMS Object Explorer. A DENY permission was the cause. Here is how I tracked it down.
SQL SERVER – Maintenance Plan failing with 0x80131904 – A network-related or instance-specific error occurred while establishing a connection to SQL Server.
After patching, a client found every Maintenance Plan failing with 0x80131904, a network-related or instance-specific error. Here is the cause and the fix.
SQL SERVER – Event ID 26 – Your SQL Server Installation is Either Corrupt or has Been Tampered With (Error Getting Instance Name)
A named instance would not start, and Event ID 26 said the install was corrupt or tampered with (Error Getting Instance Name). Here is what I found.
SQL SERVER – Fix: Error: 1934, Level 16, INSERT or UPDATE Failed Because the Following SET Options have Incorrect Settings: ‘QUOTED_IDENTIFIER’.
A query ran fine in SSMS but failed in an Agent job with error 1934: SET options have incorrect settings: ‘QUOTED_IDENTIFIER’. Here is the simple fix.
Row and Page Compression: Estimating Savings Before You Compress
Estimate row and page compression savings per index and partition, then compare storage, CPU, reads, and maintenance before deployment.
SQL SERVER – Error 17113, Severity: 16 – Error Occurred While Opening File ‘master.mdf’ to Obtain Configuration Information at Startup
I broke my own SQL Server by editing startup parameters. Here is how the ERRORLOG helped me fix error 17113, error opening master.mdf at startup.