A client’s security patch for a SQL 2005 clustered instance failed with Error 29527, unexpected error in datastore. The setup log pointed to the cause.
SQL SERVER – Error – Attempted to Perform an Unauthorized Operation
A reader’s SQL Server 2016 setup log showed ‘Attempted to perform an unauthorized operation’ during local discovery. Here is what caused it and the fix.
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.
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.