|Showing entries 1 to 30 of 32915||Next 30 Older Entries|
Hi Apache Friends!
We are happy to announce a new release of XAMPP for all platforms. This release updates the main components to the latest stable versions. You can download new versions at http://www.apachefriends.org/download.html.
We also expanded the number of BitNami-packaged applications compatible with XAMPP. In addition to the previous ones (such as[Read more...]
In a previous blog, my colleague Dimitri Vanoverbeke, discussed at a high level the concepts of database as a service, OpenStack and OpenStack’s implementation of a DBaaS, Trove. Today I’d like to delve a bit further into Trove and discuss where it fits in, and who benefits. First off, I’d like to point out that
Just to recap, Trove is OpenStack’s implementation of a database as a service (DBaaS) for its cloud infrastructure as a service (IaaS). And as the mission statement declares, the Trove project seeks to provide a scalable and reliable cloud database service providing functionality for both relational and non-relational database engines. With the current release of Icehouse, the technology has begun to show maturity providing both stability and a rich feature set.
In my opinion, there are two primary markets that will benefit from Trove; the first being[Read more...]
Disclosure -- I received a copy of this book from the publisher for review.
The MariaDB Cookbook is well written by someone who knows the MariaDB database server quite well. Writing a 300 page book by yourself is no small feat and Daniel has done it with aplomb. I am most familiar with Percona server and Oracle's MySQL server but I have been interested in MariaDB for some of its new features -- especially the multi-source replication. I took a look at this section in particular and it was well done with clear step by step instructions on how to accomplish multi-source replication. Each of the recipes follow this pattern with clear, concise steps. My only complaint about the cookbook items are that they might be that they are a little too concise at times -- although to Daniel's credit there are frequent See Also sections that point to deeper details.
As I read through the[Read more...]
The MariaDB project is pleased to announce the immediate availability of MariaDB Galera Cluster 5.5.39. This is a Stable (GA) release.
See the[Read more...]
A recurring and very common customer issue seen here at the Percona Support team involves how to make the ibdata1 file “shrink” within MySQL. I can only imagine there’s a degree of regret by some of the InnoDB architects on their design decisions regarding disk-space management by the shared tablespace* because this has been a big frustration for many MySQL users over the years.
There’s a very old bug (“InnoDB ibdata1 never shrinks after data is removed,” Sept. 8 2003) documenting user dissatisfaction. Shortly before that issue celebrated its 10th anniversary, James Day, MySQL senior principal support engineer at Oracle, posted a comment[Read more...]
While certainly not ready for production here is something to look forward to in MySQL 5.7:
"As of MySQL 5.7.5, the innodb_buffer_pool_size parameter is dynamic, allowing you to resize the buffer pool without restarting the server. The resizing operation, which involves moving pages to a new location in memory, is performed chunks. Chunk size is configurable using the new innodb_buffer_pool_chunk_size configuration option. You can monitor resizing progress using the new Innodb_buffer_pool_resize_status status variable.
MariaDB Galera Cluster involves more effort and resource to administer than standalone MariaDB systems. If you would like to learn how to better manage your MariaDB cluster, then this webinar series is for you.
We will give you practical advice on how to introduce clusters into your MariaDB / MySQL environment, automate deployment and make it easier for operational staff to manage and monitor the cluster using ClusterControl.
English - Tuesday, September 30th @ 11am CEST:[Read more...]
The Brainiac Corner is a format where we talk with some of the smartest minds in the system, database, devops, and IT world. If you have opinions on pirates, or anything else related, please don’t hesitate to contact us.
Today we interview Matt Dawson, a builder of Internet things. His current focus is client-heavy web applications, but he’s also built a slew of server-side APIs and worn the sysadmin hat from time to time. He is the Lead Software Engineer for the Web Applications team at WillowTree Apps. Previously, he worked at Convoy (née Category 4), the[Read more...]
Edit: added sample table output in MySQL
MySQL Workbench 6.2 introduces support for MS Access migration. This tutorial should help you get your Access tables, indexes, relationships and data in MySQL.
Because MS Access ODBC drivers are only available for Windows, migrating from it is also only possible from Windows. As for the destination MySQL server, you can have it in the same local machine or elsewhere in your network.
MS Access stores relationship/foreign key information in an internal table called MSysRelationships. That table is protected against read access even to the Admin user, so if you try to migrate without opening up access to it, you will get an error like this:
 [Microsoft][ODBC Microsoft Access Driver] Record(s) cannot be read; no read permission[Read more...]
With MariaDB, as with any service, you must monitor user resource usage to ensure optimal performance. MariaDB provides detailed statistics for resource usage on per-user basis that you can use for database service monitoring and optimization. User statistics are especially useful in shared environments to prevent a single gluttonous user from causing server-wide performance deterioration. If you detect abnormal use, you can apply fine-grained limits, as we'll see.
To enable user statistics in MariaDB, edit the server configuration file /etc/my.cnf.d/server.cnf. In the
[mysqld] section, add
userstat = 1, then restart the service.
Now MariaDB will gather and store usage statistics in the table USER_STATISTICS in[Read more...]
Reconfiguring replication has always been a challenge with MySQL. Each time the replication topology has to be changed, the process is tedious and error-prone because finding the correct binlog position is not straightforward at all. Global Transaction IDs (GTIDs) introduced in MySQL 5.6 aim at solving this annoying issue.
The idea is quite simple: each transaction is associated with a unique identifier shared by all servers in a given replication topology. Now reconfiguring replication is easy as the correct binlog position can be automatically calculated by the server.
Awesome? Yes it is! However GTIDs are also changing a lot of things in how we can perform operations on replication. For instance,[Read more...]
We've written a GUI application. Its command-line options are like those in the mysql client. Its graphic features are an SQL-statement text editor and a scrollable SQL result set. It runs on Linux now and we believe it could be ported to other platforms.
Here are four screenshots.
The startup is as non-GUI as can be -- in fact it gets options from the command line, or from my.cnf, the same way that the mysql client does. Wherever it seemed reasonable, we asked: What would mysql do?
It’s been three months since we announced anything for Percona Cloud Tools, not because we’ve been idle but because we’ve been so busy the time flew by! Here’s the TL;DR to pique your interest:
Percona Cloud Tools for MySQL is a hosted service providing access to query performance insights for all MySQL uses. After a brief setup, unlock new information about your database and how to improve your applications. There’s a lot more, but let’s just look at these five new[Read more...]
ScaleArc hired Percona to benchmark failover times for the ScaleArc database traffic management software in different scenarios. We tested failover times for various clustered setups, where ScaleArc itself was the load balancer for the cluster. These tests complement other performance tests on the ScaleArc software – sysbench testing for latency and testing for WordPress acceleration.
We tested failover times for Percona XtraDB Cluster (PXC) and MHA (any traditional MySQL replication-based solution works pretty much the same[Read more...]
MaxScale for MariaDB and MySQL hides the complexity of database scaling from the application. To streamline building MaxScale from source and running the test suite, you can automate the process with some useful tools to meet your needs.
I have created a Vagrant / Puppet setup that takes care of:
With this set up, a virtual MaxScale[Read more...]
Dear MySQL Users,
The MySQL Workbench team is announcing availability of the first beta
release of its upcoming major product update, MySQL Workbench 6.2.
MySQL Workbench 6.2 focuses on support for innovations released in MySQL
5.6 and MySQL 5.7 DMR (Development Release) as well as MySQL Fabric 1.5,
with features such as:
* A new spatial data viewer, allowing graphical views of result sets
containing GEOMETRY data and taking advantage of the new GIS
capabilities in MySQL 5.7.
* Support for new MySQL 5.7.4 SQL syntax and configuration options.
* Metadata Locks View shows the locks connections are blocked or waiting
* MySQL Fabric cluster connectivity – Browsing, view status, and connect
to any MySQL instance in a Fabric Cluster.
* MS Access migration Wizard – easily
You can join today's Google Hangout at http://bit.ly/1vmGR9W or watch the livestream below:
Join in #DBHangOps this Thursday, August, 21, 2014 at 11:00am pacific (18:00 GMT), to participate in the discussion about:
See all of you on Thursday!Show [Read more...]
Like you all may know, OpenStack is currently one of the coolest open source projects, so I was thrilled when I was asked to manage the deployment of an OpenStack lab for internal Percona use. Starting from basically zero, I created tasks in our Jira and assigned them to a pool of volunteer consultants. As usual in a service company, billing is the priority so I ended up losing the 2 senior guys but fortunately most of my time was with a customer that wasn’t very demanding and I could easily multitask with the project and fill the gap. So, here it goes…
To deploy the OpenStack lab we were given 8 similar servers in our Durham, N.C. offices. The specs[Read more...]
There are several ways to get ClusterControl installed on your database infrastructure, as described in the ClusterControl Quick Start Guide. One simple way is to use an installation script, install-cc.sh. This script automates the whole process, and is executed on the host where you want to install ClusterControl. By default, it assumes the host has internet connectivity during the installation process.
For users who are not able to have their[Read more...]
Replication has been one of the most popular MySQL features since it made its way into the application more than a decade ago. However, as replication implementations became more complex over time, some limitations of MySQL’s original replication mechanisms started to surface. To address those limitations, MySQL v5.6 introduced the concept of Global Transaction IDs, which enable some new, advanced replication features. MySQL DBAs were happy with this, but complained that in order to implement GTIDs you needed to stop all the servers in the replication group and restart them with the feature enabled. There are workarounds – for instance, Booking.com[Read more...]
To learn about the many factors that can affect the performance of the MySQL Database, take the MySQL Performance Tuning course.
You will learn:
You can take this 4-day instructor-led course through the following formats:
There are at least two cases when it makes sense to take an image from a corrupted hard drive as soon as possible: disk hardware errors and corrupted filesystem. Faulty hard drives can give just one chance to read a block, so there is no time for experiments. The similar picture with corrupted filesystems. Obviously something went wrong, it’s hard to predict how the operating system will behave next second and whether it will cause even more damage.
Probably the best and fastest way is to plug the faulty disk into a healthy server and save the disk image locally:
# dd if=/dev/sdb of=/path/on/sda/faulty_disk.img conv=noerrror
Where /dev/sdb is the faulty disk and faulty_disk.img is the image on[Read more...]
mysqlbackup --cloud-service=s3 --cloud-aws-region=eu-west-1 \
--cloud-bucket=meb_myserver --cloud-object-key=firstbackup --cloud-trace=0 \
--backup-dir=/tmp/firstbackup --backup-image=- --with-timestamp backup-to-image
|Showing entries 1 to 30 of 32915||Next 30 Older Entries|