The scariest word for any DBA is – Database Downtime. Every DBA who is going off duty for the day or going away on vacation for a month is always worried about Database Downtime. I totally sympathize with everyone who is constantly worried about their database’s downtime. In the real world, we all know when our database does down, it means that our business is stopped. There is no other analogy we can give.
MySQL – Connection Error – [MySQL][ODBC 5.3(w) Driver]Host ‘IP’ is Not Allowed to Connect to this MySQL Server
One of my clients contacted me for a linked server issue between SQL Server and MySQL Server. Since I mostly work with SQL Server, it was a fun installing and connecting MySQL Server. While I was trying to simulate the issue and I wanted to create a linked server. In this blog, we would learn how to fix MySQL connection error [MySQL][ODBC 5.3(w) Driver]Host ‘IP’ is not allowed to connect to this MySQL server.
SQL SERVER – AlwaysOn Automatic Seeding – Database Stuck in Restoring State
As a part of my consulting, I observed that there is a lot of interest in using AlwaysOn availability group. I have deployed many AlwaysOn solutions from start-to-finish. Recently I encountered an issue and in this blog, we would discuss reason of an availability database to stay in restoring mode even after using automatic seeding.
QL SERVER – Unable to Create Listener: Msg 41009 – The Windows Server Failover Clustering (WSFC) Resource Control API Returned Error Code 5057
One of my clients contacted me for quick On-Demand consulting. They were working under close deadlines and delivering the solution on time was critical for their success. They contacted me and explained that they were having trouble creating a listener for their two nodes AlwaysOn Availability Group. The error message which they received from T-SQL is below. Let us learn how we can fix error related to Windows Server Failover Clustering.
SQL SERVER – The Report Server Cannot Open a Connection to the Report Server Database. (rsReportServerDatabaseLogonFailed)
When my clients contact me for any issue, I always try to help them or redirect them to someone who can help them better than me. Once a client contacted me for an issue with SQL Server Reporting Services. As usual, I didnât give up, but I investigated error message and applied a logical approach to fixing it. Let us see how to fix the error related to report server database.Â
SQL SERVER – FIX: Error 14001: The Application Has Failed to Start Because its Side-by-side Configuration is Not Correct
There are so many ways to break things in the operating system. In this blog, we would learn about fixing error âThe application has failed to start because its side-by-side configuration is not correctâ.
SQL SERVER – FIX: Msg 3231 – The Media Loaded on “Backup” is Formatted to Support 1 Media Families, but 2 Media Families are Expected According to the Backup Device Specification
While preparing for a demo for my upcoming session, I encountered an interesting error. I thought I have written a blog about it, but I was wrong. My earlier blog was about a different error which looks very similar. Here is my earlier blog for error 3132. SQL SERVER â FIX: Msg 3132, Level 16 â The Media Set has 2 Media Families but Only 1 is Provided. All Members Must be Provided. In this blog post, we will learn how to fix the error The Media Loaded on “Backup” is Formatted to Support 1 Media Families, but 2 Media Families are Expected According to the Backup Device Specification.