Remove 2014 Remove Database Remove Design Remove Storage
article thumbnail

Weekend Reading: Amazon Aurora: Design Considerations for High Throughput Cloud-Native Relational Databases.

All Things Distributed

In many, high-throughput, OLTP style applications the database plays a crucial role to achieve scale, reliability, high-performance and cost efficiency. For a long time, these requirements were almost exclusively served by commercial, proprietary databases.

Database 120
article thumbnail

Using JSONB in PostgreSQL: How to Effectively Store & Index JSON Data in PostgreSQL

Scalegrid

Why should a relational database even care about unstructured data? JSON database in 9.2 It is useful to validate incoming JSON and store in the database. 2014) added support for JSONB data type. JSONB storage has some drawbacks vs. traditional columns: PostreSQL does not store column statistics for JSONB columns.

Storage 321
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

MariaDB vs MySQL: Key Differences and Use Cases

Percona

Before we dive into the differences between MariaDB and MySQL, we will provide a thorough examination of each relational database management system (RDBMS). While originally designed to be a drop-in replacement for MySQL, it evolved into its own distinct database management system and is now maintained and supported by the MariaDB Foundation.

article thumbnail

Should You Use ClickHouse as a Main Operational Database?

Percona

What if we use ClickHouse (which is a columnar analytical database) as our main datastore? Well, typically, an analytical database is not a replacement for a transactional or key/value datastore. Although such databases can be very efficient with counts and averages, some queries will be slow or simply non existent. Processed 4.15

article thumbnail

AMD EPYC Processors in Azure Virtual Machines

SQL Performance

Back on December 5, 2017, Microsoft announced that they were using AMD EPYC 7551 processors in their storage-optimized Lv2-Series virtual machines. Both of these Intel processors are special bespoke models that are not in the Intel ARK database. They feature low latency, local NVMe storage that can directly leverage the 128 PCIe 3.0

Azure 42
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). As we moved towards SQL Server 2014, the pace of hardware accelerated.

article thumbnail

SQL 2016 – It Just Runs Faster: DBCC Scales 7x Better

SQL Server According to Bob

Internally DBCC CHECK* uses a page scanning coordinator design (MultiObjectScanner.) SQL Server 2016 changes the internal design to (CheckScanner), applying no lock semantics and a design similar to those used with In-Memory Optimized (Hekaton) objects, allowing DBCC operations to scale far better than previous releases.