Remove 2016 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

New Metadata-Only Column Changes in SQL Server 2016

SQL Performance

Depending on the type of change and the configuration of the database, an ALTER COLUMN command will need to perform one of the following actions: Change metadata in system tables only. Improvements in SQL Server 2016. The subject of this post is the additional changes that are enabled for metadata-only from SQL Server 2016 onward.

Servers 63
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

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. JSONB storage has some drawbacks vs. traditional columns: PostreSQL does not store column statistics for JSONB columns. JSONB Patterns & Antipatterns.

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

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). Our design needed to scale and be adaptable to the modern hardware on the market.

article thumbnail

Expanding the AWS Cloud: Introducing the AWS US East (Ohio) Region

All Things Distributed

In the remainder of 2016 and inq 2017, we will launch another four AWS regions in Canada, China, the United Kingdom, and France, adding another nine AZs to our global infrastructure footprint. It brings the worldwide total of AWS Availability Zones (AZs) to 38, and the number of regions globally to 14.

AWS 127
article thumbnail

How To Use systemd in Linux to Configure and Manage Multiple MySQL Instances

Percona

Why not just create another database on the same instance? We split databases by function/team to give each team full autonomy over their schema, And if someone screws up, it breaks their cluster, not all databases. So you put multiple MySQL servers on a single machine instead of multiple databases inside one MySQL instance.