Error 5511 kept a production database offline after a SQL Server restart, because a FILESTREAM log record under the log folder was corrupted. We moved the corrupted file to another folder and the database came online. CHECKDB came out clean and the client saw no problems for weeks.
SQL SERVER – FIX: Arithmetic Overflow Error in Object Execution Statistics Report in Management Studio
The SSMS Object Execution Statistics report suddenly failed for a client with Msg 8115, arithmetic overflow converting to int. Here is why and what to do.
SQL SERVER – Upgrade Error – ALTER DATABASE Statement Not Allowed Within Multi-statement Transaction
A failed SQL Server 2014 SP2 left the service down with: ALTER DATABASE statement not allowed within Multi-statement Transaction. Here is how to fix it.
SQL SERVER – AlwaysOn Automatic Seeding Failure – Failure_code 15 and Failure_message: VDI Client Failed
One database would not seed to the secondary replica. Here is how sys.dm_hadr_physical_seeding_stats showed failure_code 15 and VDI Client Failed.
Backup Detected Log Corruption: Context Is Bad Middle Sector
Backup detected log corruption in a client’s database, and every full backup failed at exactly 60 percent. Instead of rebuilding the log, we checked the VLFs and found a log waiting on REPLICATION. Removing the leftover replication fixed the backup.
SQL SERVER – Mirroring Error 1456 – The ALTER DATABASE Command Could not be Sent to the Remote Server Instance
Adding a new witness server after a disaster failed with database mirroring error 1456. Here is one possible cause and what to check.
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.






![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)