Remove make-the-most-of-secondary-replicas-in-sql-server-always-on-availability-groups
article thumbnail

Make the most of secondary replicas in SQL Server Always On Availability Groups

SQL Shack

In this 31st article of the SQL Server Always On Availability Group series, we will explore how you can use the secondary replica SQL database for your workloads. We configure the SQL listener to […].

article thumbnail

Aurora vs RDS: How to Choose the Right AWS Database Solution

Percona

Now that Database-as-a-service (DBaaS) is in high demand, there are multiple questions regarding AWS services that cannot always be answered easily: When should I use Aurora and when should I use RDS MySQL ? These may be performance, high availability, operational cost, management, capacity planning, scalability, security, monitoring, etc.

AWS 52
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

SQL Server 2016 – It Just Runs Faster: Always On Availability Groups Turbocharged

SQL Server According to Bob

When we released Always On Availability Groups in SQL Server 2012 as a new and powerful way to achieve high availability, hardware environments included NUMA machines with low-end multi-core processors and SATA and SAN drives for storage (some SSDs). one without a replica).

article thumbnail

Proof of Concept: Horizontal Write Scaling for MySQL With Kubernetes Operator

Percona

The scaling, in that case, is offered by the different number of Replica nodes, no matter if using standard asynchronous replication or synchronous replication. Historically MySQL is great in horizontal READ scale. However, those solutions do not offer the same level of scaling for writes operation.

Traffic 123
article thumbnail

SQL Server I/O Basics Chapter #2

SQL Server According to Bob

​​ MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT. Copyright The information ​​ that is contained ​​ in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication.

Servers 40