Here are some view tables that are going to be in the new release of Monolith. They work with the current release though, so maybe they will be useful for DBAs that have utilized the CLI to get data out of Monolith. The new release will feature an updated Status page that shows the data from these view tables instead of the “last 25 backups”. Edit the DEFINER user as needed.


mysql> show tables;
+-------------------------+
| Tables_in_monolith |
+-------------------------+
| dbs |
| process_exec |
| process_status |
| pruning |
| system |
| users |
| view_daily_result_all |
| view_daily_result_code1 |
| view_daily_result_code2 |
| view_daily_result_code3 |
+-------------------------+
10 rows in set (0.00 sec)


mysql> show create table view_daily_result_all\G
…

Welcome to the 90th edition of Log Buffer, the weekly review of database blogs.

First, SSQA.net’s SQL Master offers his walk-through of best practices for installing SQL Server 2005, with clustering as the destination.

If you read SQL Server blogs, you already know Adam Machanic. I’m very pleased to mention his first post for the Pythian Group blog, covering the basics of minimal logging and its enhancements in SQL Server 2008.

…

I've long preferred OpenOffice for my presentations. It has functionality (like the ability to enter a group of objects I've grouped and edit just one of them) that I simply can't get in Microsoft Office, and the performance is quite good. I'm therefore happy to see version 2.4 hit public release. The good just got better, as The Register reports:

The OpenOffice.org 2.4 database, Base, now supports MS-Access 2007, while capabilities for MySQL, Oracle JDBC and native HSQL databases have been improved.

PDF handling has been improved with five export options, and Writer has been rounded out with improved "find and replace", new keyboard short cuts, and the ability to set options for printing hidden or place-holder text and for following hyperlinks.

...

Properties:

Description:

This is a global buffer where MySQL caches frequently used blocks of index data for MyISAM data. Maximum allowed size is 4GB on a 32 bit platform. Greater values are permitted for 64-bit platforms beyond MySQL …

The MySQL Workbench team has released the latest Release Candidate 5.0.15 of their new DBMS modeling tool. This includes quite a few recent bug fixes and it's now rapidly approaching the GA status. The team continues on to fix all the minor nits out there so keep your feedback coming. Heck, they'll probably have a new version by the time I post this. If you've never used a database modeling tool or have been put off by the cost or complexity of these tools in the past, you should try MySQL Workbench. Mike Zinner and his team have focused on... READ MORE

I’m still looking for new entries. I get quite a few suggestions, but not all of them make it into quiz questions. Do send in your suggestions!

The maximum row size in a MySQL table in 64kb (65,535 bytes).

A LONGTEXT or LONGBLOB column may be up to 4,294,967,296 (4G) in size.

Explain how a LONGTEXT or LONGBLOB column fits into a MySQL table.

(more…)

yeah, it is all odbc, all the time here, it seems. that is just because i can’t write about the really exciting stuff. soon!

that is not to say that releasing mysql connector/odbc 5.1.3-rc is not a huge milestone! it took us a while to get there, but we finally have a unicode-aware odbc driver that is, in our opinions, production-ready. now we just need some community feedback to find out if we are right. there are a few minor issues we know about already, but the impact of those is generally small enough that the majority of folks should not have any problems.

I can’t remember the last time i used default mkfs or mount options… oh yeah, that’s right - by accident.

Anyway… I did a little experiment today.

The filesystem is my laptop /home - XFS, 100GB, 95% used (so 5-6GB free), rather aged. This is where a lot of my MySQL development is done. Mkfs options: 128MB log, version2 log. Mount options: logbufs=8, logbsize=256k. All of this geared towards increasing metadata performance.

Why metadata performance? well… source code trees are a lot of metadata :)

So, let’s try some things: cloning a repository and then removing the repository.

Two variables are being tested: mounting the file system with nobarrier (or barrier, the default). Write barriers tell the disk to ensure write order to the platter when write cache is in use. Also testing disabling (or enabling, the default) the disk write cache.

NOTE: the last option which …

Using regular expressions for query handling can become prohibitively complex after a while. If you need to manipulate parts of a query, either you are a regexp guru (I mean it, really, someone who speaks regular expressions more fluently than English) or you find some alternatives.

MySQL Proxy ships equipped with a tokenizer, a method that, given a query, returns its components as an array of tokens. Each token contains three elements:

• name, which is a human readable name of the token (e.g. TK_SQL_SELECT)
• id, which is the identifier of the token (e.g. 204)
• text, which is the content of the token (e.g. "select").

For example, the query SELECT 1 FROM dual will be returned as the following tokens:

1:
   text          select
   token_name    TK_SQL_SELECT'
   token_id      204
2: 
   text          1
 …

I have an ingrained (possibly even genetic) aversion to stock images. Actually, not all stock: just the vacuous kind. You know what I mean: like the politically-correct, gender-balanced, racially-balanced, age-diverse ones where people are all smiling and pointing at a computer screen you can’t see. Ugh!

(Photo credit: istockphoto.com)

There are many reasons not to use images like this. I guess it’s okay in some situations — for example when you just want a smiling, attractive woman with a customer-service headset to reinforce that you’ve come to the right place for support. However, even these really don’t have to be stock images. One of my former employers used their own employees for such photos, almost exclusively, and it made the site much more real. And there are plenty of examples of companies that use photos of their own employees and get “realness” as a result. If I’m not mistaken, …