Watch your data from the top of a mountain. We take care of the machinery.
AUTO_INCREMENT primary keys are useful, because they save usthe trouble to generate a unique value for every row, delegating this task to the database. But when we reach the limit we need to take some action, or we won’t be able to insert more rows. Continue reading Monitoring that AUTO_INCREMENT values won’t reach the limit
Automating deployments with the Architecture As Code paradigm has several benefits. Let’s see some of them. Continue reading 5 benefits of Infrastructure As Code
Reducing the number of queries is important with any DBMS. There are two reasons for this: reducing the latency of applications; and reducing the workload for the database servers. Continue reading MySQL/MariaDB: use SQL properly to run less queries
MySQL 8.0 and 5.7 follow a new release policy that exposes users to important risks. They broke compatibility with Xtrabackup (again). Continue reading The risks of MySQL release policy
SQL columns can be NULL or NOT NULL. Let’s see what are the good and bad reasons to declare NULL columns. Continue reading When to use NULLable columns in relational databases
Transactions can be read only. This article explains what read only transactions are and why we should use them when appropriate. Continue reading READ ONLY transactions in MariaDB and MySQL
This article discusses how to access data from a remote table using the CONNECT storage engine, in MariaDB. Continue reading Using CONNECT to access remote MariaDB or MySQL tables
MariaDB Server Fest 2020 was a great online event for the MariaDB community. This is a review from Vettabase. Continue reading A MariaDB Server Fest 2020 review
Vettabase asked the community what is the most dangerous SQL statment. Let’s think a bit about it! Continue reading The most dangerous SQL statement
Running DROP statements in production is always dangerous. But there are some measures we can take to make them safer. Continue reading Dropping database objects in a safe way