Read on to learn basics about invalid objects and how to identify them in SQL Server, MySQL, and Oracle databases using dbForge Edge or from the command line.

The post Find Invalid Objects in Your Databases appeared first on Devart Blog.

MySQL Enterprise Edition has the ability to mask and de-identify data. Find out how to use it in this article!

Oracle Cloud Infrastructure (OCI) has a very robust always-free tier. Oracle recently announced that HeatWave MySQL will now be part of that offering. As part of the always-free tier, we can set up one instance and a single-node HeatWave Cluster. In this post, we will show how to spin up that instance and connect to it using a […]

Codership will be a sponsor at DOAG 2024 in Nuremberg, Germany. There will also be 2 Galera Cluster related talks to attend:

1. Building a Global, High-Availability Database with Galera Cluster: A Live Demo Colin Charles Codership
2. Safe Harbor! Wie der Galera Cluster ihre MySQL Datenbanken „unsinkbar“ macht. Matthias Jung Ordix

There are also a few Galera Cluster blog posts in German from our partner Ordix that are useful:

1. …

MySQL Enterprise Edition has for years featured methods for masking and de-identifying data.  Let’s explore, with examples, how to use them!   Agenda of the article     The Data Masking and De-Identification extensions of MySQL Enterprise Edition   Data masking refers to masking portions or all of the data by replacing some of its […]

By now you must have read our documentation on isolation levels and also our Support for Transaction Isolation Levels. It is worth noting that the default transaction isolation level in MySQL 8 is REPEATABLE READ.

Here is a simple example of this, in action (you can test this on two different nodes, even across a 9-node Galera Cluster!).

First we do some simple setup:

CREATE DATABASE isolate;

USE isolate;

CREATE TABLE products (
id INT PRIMARY KEY,
name VARCHAR(50),
price DECIMAL(10, 2)
);

Then we insert some initial data:

INSERT INTO products (id, name, …

Just thought I’d share a script I use daily and helps me redirect my attention if needed.

This is but a mere pointer, guideline and starting point in any task. I just thought I’d share and hope someone else’s day becomes slightly easier thanks to some brief investigation and command tweaking.

Now the really handy thing here is that I only hard code the router01 node name, as I’m using that as a potential endpoint (thinking cloud, XaaS, etc…) where it could also be a VIP, LBR or similar. It’s the entry point so I can query the P_S table error_log so I can get different views and act accordingly.

For example:

• First, give me the InnoDB Cluster ordered server list so I can take a step back from my usual pains and worries, and see the architecture view. And make me type “Y” or similar to move on. Here if there were any server missing, I’d see the summary right away so I don’t really need to …

I have been scratching my head about MySQL startup for some time.  There is much to say about this, and many other posts will probably follow.  For now, it is enough to know that with many tables (millions) the startup of MySQL 8.0+ (including 8.0, 8.4 and 9.0) is suboptimal (to say the least).  With very little changes, I was able to speed it up, from 2:39 to 1:09 (1 minute and 9

The aim of this long article is to give you the instructions and tools to migrate your production database, from your current environment to a solution based on Percona Everest (MySQL).

Nice, you decided to test Percona Everest, and you found that it is the tool you were looking for to manage your private DBaaS. For sure the easiest part will be to run new environments to get better understanding and experience on how the solution works. However, the day when you will look to migrate your existing environments will come. What should you do?

Prepare a plan! In which the first step is to understand your current environment. 

 When I say understand the current environment, I mean that you need to have a clear understanding of:

• the current dimensions (CPU/Memory/Disk utilization)
• the way it is accessed by the …

 Check and review recommended MySQL InnoDB setting using MySQL Shell for optimal Performance. 

Performance of MySQL is always top priority for each organisations because data holds valuable insight into organizational productivity and proactive decision making. High-performing databases help organizations stay ahead by enabling faster insights, quicker adaptation to changes, and superior customer experiences. When performance of MySQL is slow it impacts user experience and data driven innovation. 
Performance has different meaning at different context however it’s important to keep MySQL instance healthy by balancing the hardware vis-à-vis InnoDB settings. 
I have been asked multiple times by MySQL customer about 

1. Does MySQL has right set of InnoDB configurations ? 
   
2. What are the InnoDB parameters to tune …