Skip to main content

THE DBA NOTES

The information provided in this blog is derived from personal experiences and standard database administrator practices.

Search This Blog

Showing posts with the label Always-On

Posts

Python Runtime Installation for SQL Server 2019

Python SQL Server

+

SQL Server Error 41125

December 07, 2022

Always-On SQL Server

+

SQL Server Always-On drawbacks

December 06, 2022

+

CATEGORIES

Always-On
Azure
Database Recovery
Database Settings
Python
Query Store
SQL Server
SQL Server 2022

Popular Posts

SQL Server Error 41125

You may have encountered the Always-On error 41125 but still cannot bring online the Always-On groups. Check out this article for more information. The availability replica for availability group 'AvailabilityGroupName' on this instance of SQL Server cannot become the primary replica because the WSFC cluster was started in Force Quorum mode. Consider performing a forced manual failover (with possible data loss). (Microsoft SQL Server, Error: 41125) As a database administrator, it's important to have a plan in place for dealing with unexpected failures in your Always On Availability Groups. One option is to perform a forced manual failover, which allows you to take control of the failover process and manually failover to a secondary replica. Before you begin, it's important to understand the potential consequences of a forced manual failover. This type of failover will interrupt clie

Query Store for a Database in an Availability Group

Query Store is a new feature in SQL Server that allows users to monitor and troubleshoot performance issues in their databases. It provides a central repository for query plans, execution statistics, and runtime metrics, allowing users to easily identify and fix performance bottlenecks. In this blog post, we will discuss how to use Query Store in a database that is part of an Availability Group, and provide a T-SQL example of the settings required to enable and configure Query Store. To use Query Store in a database that is part of an Availability Group, the first step is to ensure that Query Store is enabled for the database. This can be done using the following T-SQL command: ALTER DATABASE [MyDatabase] SET QUERY_STORE = ON; Next, we need to specify the retention period for Query Store data. This determines how long Query Store data will be retained in the repository and can be set using the following T-SQL command: ALTER DATABASE [MyDatabase]

Azure CPU Monitoring With DMVs

Here we will cover how to monitor Azure SQL Database CPU performance using dynamic management views, and show how to diagnose CPU high usage. Dynamic management views (DMVs) are a valuable tool for monitoring the performance of Azure SQL Database. These views provide a wealth of information about the current state of the database, including resource usage, the performance of queries, and the health of the database. By using DMVs, you can gain insight into the performance of your database and take steps to improve it. One of the key DMVs for monitoring the performance of Azure SQL Database is the sys.dm_db_resource_stats view. This view contains information about the resource usage of the database, including CPU usage, memory usage, and storage usage. By querying this view, you can determine the current workload of the database, and take appropriate action to manage it. To view the resource usage of a database, you can use the following query: SELECT

Powered by Blogger