Showing entries 661 to 670 of 22515
« 10 Newer Entries | 10 Older Entries »
Displaying posts with tag: MySQL (reset)
Save Money in AWS RDS: Don’t Trust the Defaults

Default settings can help you get started quickly – but they can also cost you performance and a higher cloud bill at the end of the month. Want to save money on your AWS RDS bill? I’ll show you some MySQL settings to tune to get better performance, and cost savings, with AWS RDS.

Recently I was engaged in a MySQL Performance Audit for a customer to help troubleshoot performance issues that led to downtime during periods of high traffic on their AWS RDS MySQL instances. During heavy loads, they would see messages about their InnoDB settings in the error logs:

[Note] InnoDB: page_cleaner: 1000ms intended loop took 4460ms. The settings might not be optimal. (flushed=140, during the time.)

This message is normally a side effect of a storage subsystem that is not capable of keeping up with the number of writes (e.g., IOPs) required by MySQL. This is …

[Read more]
OpenLampTech issue #76 – Substack Repost

With the wide range of frameworks and CMSs, someone can always find their way and explore their interests using the LAMP stack. Welcome to this week’s OpenLampTech newsletter and content. Thanks for reading!

Custom WooCommerce and Shopify Solutions

Discover useful WooCommerce and Shopify custom solutions for your online store today at affordable prices!

Learn More

The Newsletter for PHP and MySQL Developers

Receive a copy of my ebook, “10 MySQL Tips For Everyone”, absolutely free when you subscribe to the OpenLampTech newsletter.

In OpenLampTech issue #76, we have some fantastic reads …

[Read more]
SQL Server vs MySQL: Difference, Performance, and Features

In the ever-evolving world of database management systems, SQL Server and MySQL stand as two of the most popular and widely-used solutions. Both platforms offer robust features and reliable performance, but which one is the right choice for your needs?

The post SQL Server vs MySQL: Difference, Performance, and Features appeared first on Devart Blog.

MySQL LIKE Operator: 7 Examples and Best Practices

We have been talking about different MySQL operators in their guises for quite a while now: along with WHERE condition or SELECT statement, you name it. Now, the time to shine has come for the LIKE conditional operator used to search for patterns in strings with the help of wildcard characters. In this article, we will provide the basic syntax for using LIKE, along with illustrated examples of how to apply it in queries using one of the best MySQL IDEs on the market — dbForge Studio for MySQL.

The post MySQL LIKE Operator: 7 Examples and Best Practices appeared first on Devart Blog.

Announcing MySQL Server 8.0.33

On April 18 2023, MySQL Server 8.0.33 was released. It is the latest release of our MySQL 8.0 General Availability Release. The new release introduces a few new features alongside with some deprecations, as well as bugfixes and security fixes. New MySQL Enterprise Edition Data Masking Component MySQL Enterprise Edition now provides data masking and de-identification capabilities […]

How to Persist a Hashed Format Password Inside ProxySQL

In this blog post, we will see how to persist the password inside the ProxySQL mysql_users table in hashed format only. Also, even if someone stored the password in cleartext, we see how to change those into the hashed format easily.

Here we are just highlighting one of the scenarios during work on the client environment where we noticed that the ProxySQL mysql_users table had more than 100 user entries, but some of them were available/inserted into the clear text password, whereas some were inserted properly into hashed entries.

Before just explaining those simple commands that were used to fix those clear text entries into the hashed entry quickly, let’s see some more information about the ProxySQL mysql_users table and the password formats.

Password formats inside ProxySQL

ProxySQL is capable of storing passwords in two different formats within the mysql_users.password

[Read more]
OpenLampTech issue #75 – Substack Repost

I’m learning so much each week from just running the OpenLampTech developer newsletter to reading the great content shared within. There is always something to learn and I am thankful for your reading each week.

Custom WooCommerce and Shopify Solutions

Discover useful WooCommerce and Shopify custom solutions for your online store today at affordable prices!

Learn More

If you are not yet subscribed, head on over and grab a free subscription and get the weekly OpenLampTech publication delivered straight to your inbox.

In OpenLampTech issue #75, we are looking at …

[Read more]
schemadiff: Vitess In-memory Schema Diffing, Normalization, Validation and Manipulation

Introducing schemadiff, an internal library in Vitess that has been one of its best-kept secrets until now. At its core, schemadiff is a declarative, programmatic library that can produce a diff in SQL format of two entities: tables, views, or full blown database schemas. But it then goes beyond that to normalize, validate, export, and even apply schema changes, all declaratively and without having to use a MySQL server. Let's dive in to understand its functionality and capabilities.

Fixing Errant GTID With Orchestrator: The Easy Way Out

In this article, we will discuss errant Transaction /GTID and how we can solve them with the Orchestrator tool.

Orchestrator is a MySQL high availability and replication management tool that runs as a service and provides command line access, HTTP API, and Web interface. I will not go into the details of the Orchestrator but will explore one of the features that can help us solve the errant GTID in a replication topology.

What are errant transactions?

Simply stated, they are transactions executed directly on a replica. Thus they only exist on a specific replica. This could result from a mistake (the application wrote to a replica instead of writing to the source) or by design (you need additional tables for reports).

What problem can errant transactions cause?

The major problem it causes during a planned change in a MySQL replication topology is that the transaction is not present in the binlog and hence …

[Read more]
MySQL 8.0.33: thank you for the contributions

The latest MySQL release has been published on April 18th, 2023 (my eldest daughter’s birthday).This new version of MySQL brings a new service that I’m excited to play with: Performance Schema Server Telemetry Traces Service. MySQL 8.0.33 contains bug fixes and contributions from our great MySQL community.

I would like to thank all contributors on behalf of the entire Oracle MySQL team !

MySQL 8.0.33 contains patches from Mikael Ronström, Evgeniy Patlan, Dmitry Lenev, HC Duan, Marcelo Altmann, Facebook, Nico Pay, Dan McCombs, Yewei Xu, Niklas Keller, Mayank Mohindra and Alex Xing.

Let’s have a look at all these contributions:

MySQL NDB Cluster

  • #103814 – ClusterJ partition key scratch buffer size too small – …
[Read more]
Showing entries 661 to 670 of 22515
« 10 Newer Entries | 10 Older Entries »