SQL Server Database Recovery

Why You Are Not Able to Access Database in an Availability Group in SQL Server?

Failover Condition Level determines when a failover should occur. This applies to SQL Server Always on Availability Group and to the SQL Server Failover Cluster Instances. Based on the failover condition level, you might not be able to access databases participating in Always On. Policy to failover For an availability group, automatic failovers are controlled by failover policy. With these policies, we can attain the highest level of control on the conditions that trigger a failover. In your...

Read more »

Message Handling Can Affect Your Availability Group Replicas in SQL Server

The state of databases participating in Always On are prone to change due to message handling. A sudden failover might interrupt a large transaction happening in the database that participates in Always On. This will result in a lengthy undo process and database status would be ‘Not Synchronizing’. Error message but no user action needed If your availability group is having hundreds of databases and heavy workload runs on the availability group, a sudden failover will change the status of...

Read more »

How to Scan and Get Mirrored Databases in SQL Server

For setting a SQL Server database mirroring we need two SQL Server instance. These two SQL instances can be on the same machine or on different machine. In this article, we will learn how to get the list of all mirrored databases from our SQL Server environment. Scan for Always On This script would help you to scan your SQL environment and identify SQL Server databases that are part of mirroring. In this script, we would be connecting to each linked server from a Central server. Please do...

Read more »