A Configuration Manager WMI error blocks SQL Server Configuration Manager with the message that it cannot connect to the WMI provider. This is a second way to fix it, using mofcomp with the file for your SQL Server version. If mofcomp does not succeed, my earlier post has more steps.
go-sqlcmd: The New Command Line Tool for SQL Server
Set up go-sqlcmd on Windows, verify the executable, run scripts and variables, control output, and review optional container commands.
Setup Error 1639: Invalid Command Line Argument in SQL Server
Setup error 1639 stopped my SQL Server 2019 install with an invalid command line argument message. The real clue was in the log: a component from an earlier incomplete install was still there. Uninstalling it with msiexec fixed the problem.
SQL SERVER – Script level upgrade for database ‘master’ failed because upgrade step msdb110_upgrade.sql encountered error 926, state 1, severity 25
An upgrade failed: Script level upgrade for database ‘master’ failed because upgrade step msdb110_upgrade.sql encountered error 926. I explain the cause and the fix.
SQL SERVER – xp_cmdshell and Net Use ERROR: The Local Device Name is Already in Use
Mapping a share with net use through xp_cmdshell, I hit “The local device name is already in use”. Here is what causes this error and how to solve it.
Collapsing Repeated Spaces and Line Breaks With REGEXP_REPLACE
Tabs, line breaks and a sneaky character 160 can all hide in a name that looks fine. Here is how to clean them on purpose.
Parse and Compile Time: Reading the First Line of STATISTICS TIME
Someone pastes a compile time of 24 ms and asks if the server is slow. Run it twice and watch the plan cache do its job.