SSDT for Visual Studio 2017 would not install on my new demo machine. Here is the Installation Error 0x80070002 I found in the setup log in the TEMP folder.
SQL SERVER – Unable to Start SQL Service Error: 17172 – SNIInitialize() Failed with Error 0x2
While building a lab cluster, I could not start SQL Service: Error 17172, SNIInitialize() failed with error 0x2. Here is what the ERRORLOG showed and the fix.
SQL SERVER – SQL Service Not Starting in Cluster- The System Cannot Find the File Specified
A clustered instance would not fail over because the SQL Service on Node2 did not start: the system cannot find the file specified. Here is what we found.
SQL SERVER – FIX: Msg 3009 – Could Not Insert a Backup or Restore History Detail Record in the MSDB Database
A backup finished but raised Msg 3009: could not insert a backup or restore history detail record in msdb. Here is why, with steps to reproduce it.
SQL SERVER – Incorrect Error: Unable to Add Filegroup – A Severe Error Occurred on the Current Command
A client with a huge partitioned database could not add filegroup and got Msg 0, a severe error. Here is how we found the real, much deeper issue.
Msg 217: Nested Triggers Exceed the 32 Level Limit
Msg 217 appears when triggers fire each other past the nesting limit of 32. A reader asked what happens when one trigger calls another. Two AFTER INSERT triggers show it, and both tables stay empty.
Cluster Remote Access Rule Failed During SQL Server Cluster Setup
The Cluster Remote Access rule failed while I installed a SQL Server failover clustered instance. Detail.txt showed setup could not reach a remote node. I checked the usual causes, then skipped the rule from the command line, and the install finished.