I don’t understand how this works. Can an EC2 instance manage a MySQL server installation on an RDS instance? RDS don’t even provide an option to stop/start the mysql service. RDS provides a very limited option to manage the MySQL server. Using an EC2 instance is more like tunneling into the RDS.

The home of Eurovision and Euroradio choses Severalnines to tune its MySQL databases

Stockholm, Sweden and anywhere else in the world – Severalnines, the provider of database infrastructure management software, recently announced its latest customer, European Broadcasting Union (EBU), a premium media distributor of live sports, culture, news and entertainment content. The Swedish company won the new deal in the same year as heartthrob compatriot Måns Zelmerlöw’s rendition of “Heroes” won the EBU’s flagship programme, the Eurovision Song Contest, watched by 200 million viewers.

The EBU is the world’s leading alliance of public service media with 73 Members in 56 countries across Europe and beyond. The EBU’s platform provides content creators in the broadcasting industry with high-quality …

Our team is pleased to announce the release of the upgraded versions of dbForge Fusion for SQL Server v1.9, dbForge Fusion for MySQL v6.3, and dbForge Fusion for Oracle v3.7, all with support for Visual Studio 2015.

In 0.5.0 version of MySQL Group Replication plugin, we have introduced the Auto-increment configuration/handling feature through which auto increment variables (auto_increment_increment and auto_increment_offset) are auto configured by the plugin, so that different members of the group don’t generate duplicated auto increment values.…

When MySQL 5.7.8 is built and run with the Thread Sanitizer, one of the first issues reported is a data race with MySQL's use of pthread barrier wait and pthread barrier destroy.   The data race report is:

WARNING: ThreadSanitizer: data race (pid=30104)   Write of size 1 at 0x7ffd33054298 by main thread:     #0 pthread_barrier_destroy /home/rfp/llvm/projects/compiler-rt/lib/tsan/rtl/tsan_interceptors.cc:1236 (mysqld+0x000000d5a71b)     #1 start_helper_thread …

Auditing your database means tracking access and changes to your data and db objects. The Audit Log Plugin has been shipped with Percona Server since 5.5.37/5.6.17, for a little over 12 months. Prior to the Audit Log Plugin, you had to work in darker ways to achieve some incarnation of an audit trail.

We have seen attempts at creating audit trails using approaches such as ‘sniffing the wire’, init files, in-schema ‘on update’ fields, triggers, proxies and trying to parse the traditional logs of MySQL (slow, general, binary, error). All of these attempts miss a piece of the pie, i.e. if you’re sniffing tcp traffic you’ll miss local connections, parsing binary logs you’re missing any reads. Your reasons for audit logging might be down to compliance requirements (HIPAA, PCI DSS) or you may need a way to examine database activity or track the connections incoming.

Over the past …

At our August meetup, our guest Calvin Sun gave a presentation on life @ Twitter. Some of the details of his presentation included:

Download PDF Presentation

• Information on existing data and storage solutions in operation.
• MySQL 5.6 performance improvements over MySQL 5.5
• The short upgrade cadence, most servers are running 5.6.26.
• Various patches and optimizations developed by Twitter to run at scale.
• Cotton on Mesos
• Best practices

Download Introduction Slides …

Download MariaDB 10.1.7

Release Notes Changelog What is MariaDB 10.1?

MariaDB APT and YUM Repository Configuration Generator

The MariaDB project is pleased to announce the immediate availability of MariaDB 10.1.7. This is a Release Candidate (RC) release.

See the …

The MySQL server supports a variety of client connection methods. To summarize: you have TCP/IP (v4 and v6) on all OSes (with or without TLS/SSL encryption), Unix Domain Sockets on Unix/Linux, and Named Pipes and/or Shared Memory on Windows.

Each of these connection methods has its own set of pros and cons: speed, security, portability, and ease-of-use.…

A database replication topology is never written in stone - it evolves along with your application and data. Changes are usually needed to help scale out, to distribute your database across multiple regions or data centers, or to perform software/hardware maintenance operations. The initial setup of a replication topology is simple, but as soon as you start changing it, things can quickly get complex. 

How do we fail-over our replication masters and slaves without affecting the availability and consistency of our data?

In this webinar, we will discuss how to perform replication topology changes in MySQL / MariaDB, and what the failover process may look like. We’ll also discuss some external tools you may find useful when dealing with those operations.

DATE, TIME & REGISTRATION

Europe/MEA/APAC
Tuesday, September 29th at 09:00 BST / 10:00 CEST (Germany, France, …