article thumbnail

New Metadata-Only Column Changes in SQL Server 2016

SQL Performance

When we ask SQL Server to change some aspect of a column's definition, it needs to check that the existing data is compatible with the new definition. 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
article thumbnail

What is container orchestration?

Dynatrace

Problems include provisioning and deployment; load balancing; securing interactions between containers; configuration and allocation of resources such as networking and storage; and deprovisioning containers that are no longer needed. How does container orchestration work?

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

USENIX LISA2021 Computing Performance: On the Horizon

Brendan Gregg

AWS Graviton2); for memory with the arrival of DDR5 and High Bandwidth Memory (HBM) on-processor; for storage including new uses for 3D Xpoint as a 3D NAND accelerator; for networking with the rise of QUIC and eXpress Data Path (XDP); and so on.

article thumbnail

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

SQL Server According to Bob

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. Ryan Stonecipher – Principle SQL Server Software Engineer. SQL Server.

article thumbnail

USENIX SREcon APAC 2022: Computing Performance: What's on the Horizon

Brendan Gregg

My personal opinion is that I don't see a widespread need for more capacity given horizontal scaling and servers that can already exceed 1 Tbyte of DRAM; bandwidth is also helpful, but I'd be concerned about the increased latency for adding a hop to more memory.

article thumbnail

MongoDB Rollback: How to Minimize Data Loss

Scalegrid

Recovering from a MongoDB rollback involves locating rollback files, using mongorestore to load data into a separate server, cleansing unneeded data, and importing the data back into the primary cluster, coupled with ongoing monitoring and maintenance of replica sets to maintain system health.

Database 130
article thumbnail

Use Physical Backups With MySQL InnoDB Redo Log Archiving

Percona

This issue most often occurs when there is significant MySQL server activity during the backup operation, and the redo log file storage media operates faster than the backup storage media. Enabling redo log archiving on the server requires setting a value for the innodb_redo_log_archive_dirs system variable.

C++ 101