This Log Buffer Edition makes it way through the realms of Oracle, SQL Server and MySQL and brings you some of the blog posts.
Oracle:
Introducing Oracle Big Data Discovery Part 3: Data Exploration and Visualization
FULL and NO_INDEX Hints
Base64 Encode / Decode with Python (or WebLogic Scripting Tool) by Frank Munz
Why I’m Excited About Oracle Integration Cloud Service – New Video
Reminder: …
[Read more]For years, MySQL replication used to be based on binary log events - all a slave knew was the exact event and the exact position it just read from the master. Any single transaction from a master may have ended in different binary logs, and in different positions in these logs. It was a simple solution that came with limitations - more complex topology changes could require an admin to stop replication on the hosts involved. Or these changes could cause some other issues, e.g., a slave couldn’t be moved down the replication chain without time-consuming rebuild process (we couldn’t easily change replication from A -> B -> C to A -> C -> B without stopping replication on both B and C). We’ve all had to work around these limitations while dreaming about a global transaction identifier.
GTID was introduced along with MySQL 5.6, and brought along some major changes in the way MySQL operates. First of all, every transaction has …
[Read more]DBAs often encounter situations where they need to kill queries to ensure there are no long-running queries on a MySQL server that would impact performance. Long-running queries can be the result of many factors. Fortunately, Percona Server contains some handy tools to remove problematic MySQL processes. I will highlight all of the tools via some examples in this post.
pt-kill:
There have been some good posts on this blog about the pt-kill
tool, like this one by Arunjith Aravindan titled “How a set of queries can be killed in MySQL using
Percona Toolkit’s pt-kill.” Let’s dive into pt-kill a bit further with a few more …
This past weekend we had the pleasure of attending Scale13X in Los Angeles. It was full of great conversations with solid people, and it was nice to escape the winter cold for a couple days.
Baron Schwartz presented on VivdCortex’s approach to building a time-series database in MySQL. The talk is titled Scaling VividCortex’s Big Data Systems on MySQL, and the recording and video can be seen here. If you are not automaticaly directed, Baron’s presentation begins at 5:49:00.
Below are the slides and a brief description to pique your interest.
In this talk, Baron Schwartz discusses VividCortex’s unique time-series data requirements and implementation, including:
The General Availability of MySQL Cluster 7.4 has just been announced by Oracle.
The MySQL team at Oracle are excited to announce the General Availability of MySQL Cluster 7.4, ready for production workloads.
MySQL Cluster 7.4.4 can be downloaded from mysql.com and the release notes viewed in the MySQL docs.
Figure 1 provides a summary of the enhancements delivered in this release:
MySQL Connector/Python 2.1.1 took a while to release and that was because we had to add some more packages which contains the optional C Extension. Note that this is still Alpha and we want you guys to report any problems and requests.
The Connector/Python C Extension was added because in certain situations, for example reading a huge result set, can take a long time with pure Python. That’s why we choose to interface with Connector/C (libmysqlclient).
Note: Pure Python is still default and it will be kept that way!
Installing Connector/Python 2.1 didn’t change much:
shell> python setup.py install
If you’d like …
[Read more]MySQL Connector/Python 2.1.1 took a while to release and that was because we had to add some more packages which contains the optional C Extension. Note that this is still Alpha and we want you guys to report any problems and requests.
The Connector/Python C Extension was added because in certain situations, for example reading a huge result set, can take a long time with pure Python. That’s why we choose to interface with Connector/C (libmysqlclient).
Note: Pure Python is still default and it will be kept that way!
Installing Connector/Python 2.1 didn’t change much:
$ sudo python setup.py install
If …
[Read more]MySQL Connector/Python 2.1.1 took a while to release and that was because we had to add some more packages which contains the optional C Extension. Note that this is still Alpha and we want you guys to report any problems and requests.
The Connector/Python C Extension was added because in certain situations, for example reading a huge result set, can take a long time with pure Python. That’s why we choose to interface with Connector/C (libmysqlclient).
Note: Pure Python is still default and it will be kept that way!
Installing Connector/Python 2.1 didn’t change much:
sh $ sudo python setup.py install
…
[Read more]