THE DBA NOTES

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...

SQL Server 2022 new features

SQL Server 2022 is an upcoming release of Microsoft's popular relational database management system. This release includes several new features designed to improve performance, security, and reliability. Here are some of the key new features in SQL Server 2022: Always Encrypted with Secure Enclaves: This new feature allows users to encrypt sensitive data, such as credit card numbers and social security numbers, without sacrificing performance. Additionally, the data can be decrypted only by authorized users, using secure enclaves within the database engine. This provides an extra layer of security for sensitive data. Adaptive Query Processing: This feature uses machine learning algorithms to automatically adjust the execution plan of a query, in order to improve its performance. This can help to reduce query execution time and improve the overall performance of the database. Resumable Online Index Rebuild: This feature allows users to pause and resume rebuilding an index, without ...

SQL Server Database Recovery Pending

If you're a SQL Server database administrator, you may have encountered the dreaded "recovery pending" status on one of your databases. This can be a frustrating and difficult problem to fix, but there are a few methods you can try to get your database back up and running smoothly. One common cause of recovery pending is a lack of available log space. When a database is in recovery, it needs to have enough log space to roll forward any uncommitted transactions and bring the database back to a consistent state. If there isn't enough log space available, the recovery process will be unable to be complete and the database will remain in recovery pending. To fix this problem, you can try increasing the size of the log file. This will give the recovery process more space to work with and may allow it to complete successfully. To increase the size of the log file, you can use the ALTER DATABASE command in SQL Server Management Studio. ...

Powered by Blogger