Showing entries 17021 to 17030 of 44138
« 10 Newer Entries | 10 Older Entries »
Old repositories

Just as one does, I was finding stuff to delete and I stumbled across this old directory which had dozens of BitKeeper work directories. Of course, I don't have a valid license for BitKeeper anymore and these directories haven't been touched in years!

I guess I shall sit on them for a while.

Collaborate 2012 – Day 3

Virtualization is important and Dave Welch from the House of Brick gave a great presentation of experiences with VMWare and Tier 1 databases. It was a comprehensive presentation, but the white paper was easier to follow. The slides were complete but the volume of information was a lot for an hour presentation. Well worth the time though.

Utah Oracle User Group (UTOUG) announced a call for Fall Symposium papers today. The Fall Symposium will be in Salt Lake City on 9/6/2012. If you’re interested in presenting on Oracle or MySQL, the call for presentations will be open until 6/15/2012.

The conference party was tonight, and it provided some nice orderves and pizza. The theme was a return to 1980s music, and …

[Read more]
An old way of sandboxing MySQL

While preparing for the yesterday's MySQL/MariaDB 5.5 talk at the Mail.Ru technical forum, I downloaded the source code of three 5.5 forks - Oracle, Percona and MariaDB. And was happy that my g'old way of sandboxing an instance without installing it still works.

I don't know whether MySQL sandbox is using this approach under the hood, here it goes:

1. Make sure /etc/mysql/my.cnf is not present or commented out.
2. Create a ~/.my.cnf with few important lines:

[client]
port        = 3307
host        = 127.0.0.1
socket      = /opt/local/var/mysql/mysql.sock

[mysqld]
gdb # this one is necessary just to sandbox
max_allowed_packet=16M
port=3307
socket=/opt/local/var/mysql/mysql.sock
language=/home/kostja/work/mariadb/5.5/sql/share/english
character-sets-dir=/home/kostja/work/mariadb/5.5/share/charsets …
[Read more]
MySQL at Collaborate 12 — Day 3

Collaborate 12 is in Vegas and Collaborate 13 will be in Denver. Mark your calendars now!

The last MySQL session for this year’s Collaborate is over. There is another day of sessions to go but they will go on without MySQL-centric topics. The majority of those the MySQL Community Team have talked to are Oracle professionals looking to expand their support for existing MySQL instances in their organizations or those looking to move some aspect of their data over to MySQL. Many use Collaborate for obtaining technical information as they feel Oracle Open World is too frenzied to get niyty gritty details. Attendance at MySQL sessions were much larger than last year and demo pod booth action was heavy with those seeking specific answers to their questions. And they were seeking details on the NoSQL/SQL InnoDB/NDB interface, operational …

[Read more]
Testing STEC SSD MACH16 200GB SLC

Following my previous benchmark of Samsung 830, today I want to show results for STEC MACH16 SATA card, 200GB size, this card is based on SLC, and regarding STEC website, it is an enterprise grade storage.

For tests I use sysbench fileio, 16KiB block size (to match workload from InnoDB, as this is primary usage for me), and recently I switched to use async IO mode. There are two reasons for that. First, MySQL/InnoDB uses async writes, so this will emulate database load, and second, async mode allows to see maximal possible throughput, it does not show reliable latency though, as it appears there is no a reliable way in the Linux asynchronous IO library to get time metrics for particular IO …

[Read more]
YEAR(2) Challenge

You might remember this little thing called the Y2K bug.  That’s twelve years ago, but MySQL still supports a YEAR(2) data type.  A recent internal discussion made me realize there were aspects of YEAR(2) that I didn’t fully understand, and prompts me to challenge readers to come up with a truly viable use case for YEAR(2) data types.

A primary reason for storing only the last two digits of years is to save on storage space, so perhaps YEAR(2) makes sense for big data or in situations where storage is constrained, right?  Well, no – the number of bytes used to store YEAR(2) data is the same as what is required when YEAR(4) is used:

mysql> SHOW CREATE TABLE y2\G
*************************** 1. row ***************************
Table: y2
Create Table: CREATE TABLE `y2` (
`y` year(2) DEFAULT NULL
) ENGINE=MyISAM DEFAULT CHARSET=latin1
1 row in …
[Read more]
Interest building in Percona XtraDB Cluster

In the last few weeks I’ve been caught off guard by the number of people who’ve told me they have been evaluating Percona XtraDB Cluster (link), and even more surprised at the projects they’re considering it for. Yesterday alone I spoke to several people who have been evaluating it for large, mission-critical enterprise deployments. Some new, some to replace existing systems that use standard MySQL replication. What was interesting is that some people said they’ve been putting it through its paces for months – before we even released it as GA.

Webinar 5/2: Advanced Multi-Master Solutions Made Easy with Continuent Tungsten

Webinar, Wednesday 5/2 @ 10 am PT/1pm ET

Continuent Tungsten has broken new ground to make previously complex or completely unattainable MySQL data management solutions simple and easy to deploy. Continuent Tungsten brings high availability, performance scaling, and simple cluster management to off-the-shelf MySQL. Continuent Tungsten also includes advanced multi-master topologies that

Testing Samsung SSD SATA 256GB 830 – not all SSD created equal

I personally like PCIe based Flash, but from a pricing point our customers are looking for cheaper alternatives. SATA SSD is an options. There is many products based on MLC technology, and Intel 320 I would say is the most popular. I do not particularly like its write performance – I wrote about it before, that’s why I am looking for comparable alternatives. Samsung 830 256GB looked like a good product, that’s why I decided to test it.

For tests I use sysbench fileio, 16KiB block size (to match workload from InnoDB, as this is primary usage for me), and recently I switched to use async IO mode. There are two reasons for that. First, MySQL/InnoDB uses async writes, so this will emulate database load, and second, async mode allows to see maximal possible throughput, it does not show …

[Read more]
Managing MySQL Backups

Database backups are typically critical to organizations, and are an important part of an overall disaster recovery strategy.

MySQL Enterprise Backup performs online "Hot", non-blocking backups of your MySQL databases, and interfaces with media management software such as Symantec NetBackup, Oracle Secure Backup and IBM Tivoli Storage Manager to execute backup and restore operations.

Two new white papers are available to help you better understand:

Enjoy the white papers.

Showing entries 17021 to 17030 of 44138
« 10 Newer Entries | 10 Older Entries »