2016 Code Database Storage 
SQL Server According to Bob
SEPTEMBER 26, 2016
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). Direct seeding of new database replicas. one without a replica).
Dynatrace
OCTOBER 15, 2021
The data is incredibly plentiful and difficult to store over long periods due to capacity limitations — a reason why private and public cloud storage services have been a boon to DevOps teams. Cloud databases excel at storing large volumes of information for later reference, and this data often has business value or privacy restrictions.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
SQL Performance
MAY 1, 2020
In a recent tip , I described a scenario where a SQL Server 2016 instance seemed to be struggling with checkpoint times. I was a bit perplexed by this issue, since the system was certainly no slouch — plenty of cores, 3TB of memory, and XtremIO storage. Change the Target Recovery Time of a Database.
Percona
JANUARY 24, 2023
Some of the built-in features ( wal_compression ) have been there since 2016, and almost all backup tools do the WAL compression before taking it to the backup repository. Such “torn pages” are corruptions from the database point of view. This warning may mainly apply to users building their PostgreSQL from source code.
Percona
JUNE 4, 2023
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.
SQL Server According to Bob
DECEMBER 18, 2018
Durability: “In database systems , durability is the ACID property which guarantees transactions that have committed will survive permanently. Microsoft SQL Server Database Engine Input/Output Requirements. Device level flushing may have an impact on your I/O caching, read ahead or other behaviors of the storage system.
SQL Performance
MAY 29, 2019
From SQL Server 2016 onward, FastLoadContext is enabled by default ; the trace flag is not required. For more background, see the Data Performance Loading Guide and the Tiger Team notes on the behaviour changes for SQL Server 2016. FastLoadContext can be disabled on SQL Server 2016 using documented trace flag 692. The sqllang!CUpdUtil::FOptimizeInsert
Expert insights. Personalized for you.
40 
Let's personalize your content