To install SSMS, download the installer, run it, and connect to your server. This post explains why SSMS is separate from the SQL Server engine, how to fill in the first connection, what to do about the certificate error, and how to check the connection with one query.
SQL SERVER – FIX: Setup Was Not Able to Access Domain
A DBA installing SQL Server 2012 on a virtual machine got ‘Setup was not able to access domain’. Here is what the message means and how to get past it.
Checking That a Patch Really Installed
Checking That a Patch Really Installed means comparing full versions, reading Setup summary logs, and confirming the startup error log.
Automating SQL Server Patching With PowerShell
Automating SQL Server Patching with PowerShell means staging a verified package, running Setup quietly, checking logs, and stopping on failure.
Installing SQL Server Silently From the Command Line
Installing SQL Server silently takes a reviewed ConfigurationFile.ini, required setup switches, and a check of logs and active instance settings.
System Configuration Checker WMI Error: Fixing SQL Server Setup
Setup stopped with a WMI message before installing anything? Here are the safe repair steps, in order, with a quick check at the end.
Slipstreaming Updates Into a New Install
Slipstreaming Updates lets SQL Server Setup apply a selected CU during installation with UpdateSource and avoids a separate patch pass.