This article is the follow-up on discussion started around MySQL 5.7 results on OLTP_RW Benchmark.. -- the point was about the impact of PERFORMANCE_SCHEMA (PFS) enabled, and InnoDB checksums on MySQL 5.7 performance within this OLTP_RW workload.

As promised, here are the results:

Just in case if the legend naming in graphs is not obvious :

• PS-off : "performance_schema=off" was used
• PS-def : "performance_schema=on" was used (default PFS instrumentation)
• chksum0 : "innodb_checksums=0" was used
• chksum1 : "innodb_checksums=0, innodb_checksum_algorithm=crc32" was used

OLTP_RW 1M x8-tables MySQL 5.7 (config: trx_commit=2 double_write=0) :


OLTP_RW 1M x8-tables MySQL 5.7 …

Sometimes you require to change date format in your laravel app we have to use Carbon class for change format in laravel because it provide many date function for like change date formate count diffrence between two dates in days etc So Basically i am going to show you change date format using

MySQL has supported the GET_LOCK() function for a large part of its history. As the manual notes, GET_LOCK() can be used to implement application locks or to simulate record locks.

Changes in MySQL 5.7

In MySQL 5.7 we improved GET_LOCK() to be based on our internal meta-data locking system (MDL).…

The Severalnines team is pleased to announce the release of ClusterControl 1.2.12.

This release contains key new features, such as support for the latest versions of MySQL, MariaDB, MongoDB & PostgreSQL, operational reports and enhanced backup options, along with performance improvements and bug fixes.

Highlights

• New for MySQL, MariaDB, MongoDB & PostgreSQL
  • Operational Reports
  • Local Mirrored Repositories
  • Enhanced Backup Options
• New for MySQL
  • Support for Oracle 5.7
  • New Replication Features for Master & Slave
  • Manage Garbd and MaxScale configurations
• New for MariaDB
  • Support for 10.1
  • SSL Encryption of Galera Replication Links …

This blog will address how the MariaDB Auditing Plugin can help monitor database activity to help with security, accountability and troubleshooting.

Why Audit Your Databases?

Auditing is an essential task for monitoring your database environment. By auditing your database, you can achieve accountability for actions taken or content accessed within your environment. You will also deter users (or others) from inappropriate actions.

If there is any bad behavior, you can investigate suspicious activity. For example, if a user is deleting data from tables, the admins could audit all connections to the database and all deletions of rows. You can also use auditing to notify admins when an unauthorized user manipulates or deletes data or that a user has more privileges than expected.

Auditing Plugins Available for MySQL

As Sergei Glushchenko said in a …

Now i show you how to create CRUDCreate Read Update Delete using AngularJS and Laravel 5 In Following step by step you can create web application of create edit delete lists search with pagination of items modules In this post through you can make simple crud search and pagination module

Saturday I was in my favorite grocery store, standing in the line, browsing the net on my phone. I read Vadim Tkachenko‘s blog post about Measuring Percona Server Docker CPU/network overhead and his findings were opposite than mine – he didn’t found any measurable difference. Reading his post, he did found huge impact in networking […]

There’s still time to sign up for our webinar on Tuesday next week, February 23rd, on the scalable, open source database infrastructure behind CloudStats.me. Our friends from WooServers will be giving an overview of their project at cloudstats.me and discussing their past infrastructure challenges of scaling MySQL “write” performance with minimal cost, performance overhead and database management burden. The session will cover how they came to choose a MariaDB with MaxScale and HAProxy clustering solution, and how they leveraged ClusterControl. Sign up below:

Registration, Date & Time Europe/MEA/APAC

Tuesday, February 23rd at 09:00 GMT / 10:00 CET (Germany, France, Sweden)
…

I use Pingdom's free service to monitor slaptijack.com. Apparently, late Friday night, oom-killer decided that the server needed more memory and took out the MySQL server. To make matters worse, I missed the alarm from Pingdom, and slaptijack.com was down for pretty much all of Saturday. The fact that oom-killer was invoked is annoying, but more on that later.

The beauty of using Pelican rather than Wordpress (or any other database-driven content engine) is one less point of failure for the site. Obviously, I don't have all of slaptijack.com converted to Pelican yet (and perhaps never will), but at least parts of the site were up and working despite MySQL being down. If nothing else, this incident is enough to convince me that moving to Pelican was a good idea.

OOM'ed

…

Not so long ago I had a customer who experienced data loss after MySQL restart. It was really puzzling. MySQL was up & running for many months, but after the customer restarted MySQL server all tables have gone. The tables were still visible in SHOW TABLES output, but they were not readable:

mysql> show tables like 'actor';
+--------------------------+
| Tables_in_sakila (actor) |
+--------------------------+
| actor                    |
+--------------------------+
1 row in set (0.00 sec)

mysql> select * from actor;
ERROR 1146 (42S02): Table 'sakila.actor' doesn't exist
mysql>

To understand what’s happened let make some experiments (WARNING: Don’t do it on production or with valuable data).

Let’s take a healthy MySQL instance with installed sakila database.

While MySQL is …