One of my clients was using Always On availability group. They were having 3 nodes Always On AG setup. For simplicity, let’s call them Node1, Node2 and Node3. The first two nodes were in one subnet and node3 was in separate subnet. Let us learn about availability group failover.
SQL SERVER – FIX: SQL Service Does Not Start After Promoting the Machine as Domain Controller
One of my blog reader contacted me to check if I can help him via phone to fix a show-stopper issue with SQL Server. I offered him On Demand (55 minutes) and he readily accepted it. Let us learn in this blog post how to fix an error related to domain controller.
SQL SERVER – FIX: Msg 15150 – Cannot Alter The User ‘dbo’.
One of my clients was deploying SharePoint and they were following some documents to make sure it is as per their standard deployment. They were seeing below error while updating the login from dbo to some other login from user mapping window (for login properties window). Let us learn how to fix error 15150 about cannot alter the user.
SQL SERVER – Msg 3225: Use of WITH CREDENTIAL Syntax is Not Valid for Credentials Containing a Shared Access Signature
One of my blog readers was having trouble with backup to URL using SAS token. He followed my below blog to fix his issue. SQL SERVER – Backup to URL error: Operating system error 50(The request is not supported.) Now let us look in this blog post how we can fix errors related to credentials.
SQL SERVER – Always On Availability Group Error 35250: The Connection to the Primary Replica is Not Active
Along with my performance consulting, I have also assisted many clients in fixing some quick issues. You can refer for various consulting services which I provide. During my consulting with various clients about Always On deployment, one of the commonly reported errors as below. (I have changed the AG Name, Node names to be more generic). Below came when we used the wizard to create an availability group. Let us learn how to fix error related to primary replica.
SQL SERVER – Fix the Error – Accessing this Server via SQL Management Objects (SMO) or Distributed Management Objects is Currently Not Permitted
Sometimes when we do some unexpected things with SQL Server, you would get messages as well which are never seen earlier. One of my client was trying to implement STIG for SQL 2016 and then someone reported below error in SSMS while connecting to SQL. Let us learn about how to fix the error Accessing this Server via SQL Management Objects.
SQL SERVER – Unable to Launch SSMS Error – Cannot Find One or More Components. Please Reinstall the Application
I had SSMS 17.1 installed on the machine and it was working fine. I don’t remember what I installed, but I started facing an SSMS error.