SSMS on my laptop could not connect to SQL in Azure Virtual Machine, even though it worked fine on the VM itself. Here is how I fixed the connection.
SQL SERVER – Maintenance Plan Error: Failed to Acquire Connection “Local Server Connection”.
None of the maintenance plans worked, though the jobs ran fine. The error was failed to acquire connection “Local server connection”. Here is why.
![MySQL - Connection Error - [MySQL][ODBC 5.3(w) Driver]Host 'IP' is Not Allowed to Connect to this MySQL Server](https://blog.sqlauthority.com/wp-content/uploads/2018/03/mysql-login-err-04.jpg)
MySQL – Connection Error – [MySQL][ODBC 5.3(w) Driver]Host ‘IP’ is Not Allowed to Connect to this MySQL Server
Setting up a linked server to MySQL, the ODBC test failed: Host ‘IP’ is not allowed to connect to this MySQL server. Here is how I fixed it.
SQL SERVER – The Report Server Cannot Open a Connection to the Report Server Database. (rsReportServerDatabaseLogonFailed)
A report viewer failed with rsReportServerDatabaseLogonFailed: the report server cannot open a connection to the report server database. Here is the fix.
SQL SERVER – Unable to Connect to SQL Server in Azure Virtual Machine from SSMS on On-Premise Machine
Can’t connect from SSMS on your own machine to SQL Server in an Azure Virtual Machine? Here is the network-related error users see and what to check to fix it.
Kill All Processes for a Database in SQL Server
To kill all processes for a database, set it to SINGLE_USER with ROLLBACK IMMEDIATE and then back to MULTI_USER. This post tests that method against two open sessions, compares it with a KILL script and with RESTRICTED_USER, and explains when each one fits. It also covers what the killed sessions see and why you should not do this on production without asking.
SQL SERVER – Error: 17142 – SQL Server Service has Been Paused. No New Connections Will be Allowed
What happens when you pause the SQL Server service? Error 17142 appears and no new connections are allowed, while existing users keep working. Here is the fix.