One of my clients asked an interesting question. It took a while for me to figure out the answer so sharing with my blog readers. In this blog, we would learn how to change authentication mode of SQL Server using T-SQL query instead of SQL Server Management Studio.
SQL SERVER – Always On AG – HADRAG: Did not Find the Instance to Connect in SqlInstToNodeMap Key
During my On Demand (50 Minutes) consultancy, I solve the issue which seems quick to my client. SQL not starting, AlwaysOn not failing over, Cluster not working are few of quick things where my clients engage me. In this blog, I would share a situation where Always On Availability Group was not coming online due to error – Did not find the instance to connect in SqlInstToNodeMap key.
SQL SERVER – Timeout Occurred While Waiting for Latch: Class FGCB_ADD_REMOVE
One of my clients contacted me to resolve an issue where they were seeing these errors few minutes after restarting SQL Server Service. In this blog, we would learn about how to fix error Timeout occurred while waiting for latch: class FGCB_ADD_REMOVE.
Azure Virtual Machine – You Must Change Your Password Before Logging On The First Time
One fine day when I tried connecting to my Azure Virtual Machine in a cloud, I was welcomed with this error message.
SQL SERVER – SQL Server Management Studio Crash While Using Backup to URL or Connecting to Storage
Recently, as a part of my on-demand consulting, I was helping a client who was into a disaster situation and there was an urgent need to restore the backup of a database which was taken in Azure Blob Storage. In this blog, we will learn about how to fix the crash of SQL server Management studio while using a backup to URL or connecting to storage.
SQL SERVER – Event ID: 2004 – Resource Exhaustion Diagnosis Events
Recently I was working with a client where they were having an issue with SQL Server memory usage. They received below warning message in System Event log –Â Resource Exhaustion Diagnosis Events.
SQL SERVER – Event ID: 10028 – SQL Server Distributed Replay Client – DCOM was Unable to Communicate with the Computer
Sometimes there are many errors in the event logs which we ignore, and they fill up complete event log. When we have some issue and data is needed for root cause analysis, we do not see the actual data because its overwritten by meaningless messages. In this blog, we would learn how to fix Event ID: 10028 – SQL Server Distributed Replay Client – DCOM was unable to communicate with the computer.