#DBHangOps 4/10/13 (pre-Percona Conference!)

Annnnnd here’s the recording:

Hey all!

The Percona Live MySQL Conference and Expo is coming up in 2 weeks, meaning the last of preparations are under way. In the meantime, #DBHangOps is coming your way on Wednesday at 12:00pm PDT (19:00 GMT) with:

  • Talk about Performance Schema from Mark Leith
  • Some discussion on how people use and manage MySQL slow query logs in their environments
  • Filesystems and MySQL — which do you use, why, and how
  • What you’re excited about at Percona Live!

As always, hit up this twitter search or this blog post to grab the google hangout link to join!

See y’all on Wednesday!

Posted in computing, database, mysql Tagged with: , , , ,

#DBHangOps 3/27/13!

Hi everyone!

Here’s a video of this week’s #DBHangOps:

March 27th at 12:00pm PDT (19:00 GMT) is when the next #DBHangOps is gonna go down. Check out the twitter search and hop on the google hangout to contribute some discussion! This week’s topics are:

Catch all of ya on the google hangout! 🙂

Posted in computing, database, debugging, linux, mysql Tagged with: , , , ,

#DBHangOps Madness! 3/13/13

Here’s the recording!


March 13th at 12:00pm PDT (19:00 GMT) is the time to check in and hop online for #DBHangOps this week. Keep an ever watchful eye on the twitter search and hop on the google hangout to contribute some discussion! This week’s topics are:

  • Monitoring
    • What do you consider to be “standard” nagios checks for MySQL
  • Demos of Anemometer and MySQL Enterprise Monitor
  • Daily pain MySQL Bugs and Gotchas (e.g. show table status being cached)
  • MySQL 5.6

See all of ya on the google hangout! 🙂

Posted in computing, database, mysql Tagged with: , , , ,

#DBHangOps 02/27/13 <3

EDIT: Video from today’s #DBHangOps!

Hey there peeps!

February 27th at 12:00pm PST it is! Check back here for more info and keep a watchful eye on the twitter search (and feel free to join the conversation!). The topics we’re looking to cover this week are:

Looking forward to seeing all of you DBAs on the google hangout! 🙂

Got a fun #DBHangOps planned for this week, Wednesday 02/13/12 at 12:00pm PST. Be sure to hit up this blog post tomorrow or check this twitter search to grab the link to join the Google Hangout.
Looking to bump this to either February 20th or February 27th.

Posted in computing, database, linux, mysql Tagged with: , , , ,

#DBHangOps on 1/30/13 \o/

UPDATE: Here’s the recording, enjoy!

Hello everybody!

#DBHangOps coming at you this week, Wednesday 1/30/12 at 12:00pm PST. Be sure to check out this blog post tomorrow or check this twitter search to grab the link to join the Google Hangout.

This week’s topics were:
* bug fixes in recent versions
* Plugins
** authorization plugins (e.g. LDAP)
** audit plugin API — http://dev.mysql.com/doc/refman/5.5/en/writing-audit-plugins.html
*** state transitions of records in MySQL with a plugin?
* InnoDB Status variables from twitter — https://github.com/twitter/mysql/wiki/InnoDB-Status-Variables
* Table alters/schema changes
** Twitter patch for non-blocking alter table (throws a different error than “lock_wait_timeout”) — https://github.com/twitter/mysql/wiki/Change-History#wiki-5.5.28.t8
** Schemanator from Etsy — http://codeascraft.etsy.com/2013/01/11/schemanator-love-child-of-deployinator-and-schema-changes/
** Online Table Alter in Oracle MySQL 5.6 — https://blogs.oracle.com/mysqlinnodb/entry/innodb_full_text_search_performance
** Twitter MySQL management tools — https://github.com/jeremycole/mysql_management_tools
* Troubleshooting queries book link — http://www.amazon.com/MySQL-Troubleshooting-What-When-Queries/dp/1449312004/ref=sr_1_1?ie=UTF8&qid=1359579540&sr=8-1&keywords=mysql+sveta+troubleshooting

Posted in computing, database, linux, mysql Tagged with: , , , ,

#DBHangOps on 01/16/13!

Update: Recording!

Finally, the end of year madness is over and we’re in a fresh new year. That must mean it’s time to get back into #DBHangops! Tune in on Wednesday, 1/16/13 at 5:00pm PST to get in on the fun and share your experiences.

Check back on this blog post tomorrow or check this twitter search to grab the link to join the Google Hangout.

Topics for this weeks hangout include:
* triggers: maintenance, problems, etc.
* Oracle MySQL utilities (similar to Percona toolkit)
** Slideshow of MySQL utilities
* Database caching and cache expiration
* InnoDB log file size
** http://www.mysqlperformanceblog.com/2011/04/04/innodb-flushing-theory-and-solutions/
** http://www.mysqlperformanceblog.com/2008/11/21/how-to-calculate-a-good-innodb-log-file-size/
** http://www.mysqlperformanceblog.com/2011/09/18/disaster-mysql-5-5-flushing/
* one-liners
* Geoff’s shameful plug about a MySQL client patch he wrote! — https://gist.github.com/4508084

Posted in computing, database, linux, mysql Tagged with: , , , ,

#DBHangOps 11/28/12

Now that the thanksgiving holiday is over, it seems like the perfect time to have another #DBHangOps. If you’re interested, check this twitter search or check back on my blog here for a link to the google hangout.

Items currently on our agenda for today:
* Data corruption!
* Monitoring — what do you monitor, why, etc.
* Query killing — do you kill queries in production regularly, or in emergencies?
* Fun or useful configurations

Looking forward to chatting about MySQL stuff today!
Fun time hitting these topics this week. Check out the recording:

Posted in computing, database, linux, mysql Tagged with: , , , , , , , , , ,


Woooo, just wrapped up another night of #DBHangOps, check out the video:

For those of you who aren’t familiar with this awesome series of videos, it’s a bi-weekly meeting of MySQL DBAs via a Google Hangout to simply talk about databases (specifically MySQL). The discussions range anywhere from silly stories to awesome learnings and even little gotchas to know about when working with MySQL operationally. If you’re interested in catching when the next #DBHangops will happen, check MySQL planet for a blog post about it, or check this twitter search.

We look forward to talking with you!

Posted in computing, database, linux, mysql Tagged with: , , , , ,

Deploy image files to Amazon Web Services

Just pushed a copy of the script I’ve been working on for a couple weeks to github. The goal of the script is to push an image file containing an operating system to Amazon’s Web Services Elastic Compute Cloud so you can run the image through Amazon’s service. A lot of the development of this was based around existing documentation and blogs written by many other posters, so I finally synthesized all this information into a “simple” BASH shell script that automates the process. Take a look at it at the following link!


I’ll be sure to beef this entry up a little more about what information I referenced to develop the script and probably more on its use!

Posted in bash, computing, linux, programming, RIT Tagged with: , , , , , , , , ,

XSL to extract DOCX comments into plain text

So..this was an impromptu project I slapped together in about 20 minutes to extract comments out of a DOCX file. I ended up doing this because I stored answers to lab questions as comments in a DOCX and one of the graders I work with needed the comments in plain text….so I recalled the XSL for converting DOCX to LaTeX from my last post and wrote up a new stylesheet to extract comments. Hereeee it is!

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
    xmlns:xd="http://www.oxygenxml.com/ns/doc/xsl" version="1.0"
    <xd:doc scope="stylesheet">
            <xd:p><xd:b>Created on:</xd:b> Apr 25, 2011</xd:p>
            <xd:p><xd:b>Author:</xd:b> Geoffrey Anderson</xd:p>
            <xd:p><xd:b>E-mail:</xd:b> geoff@geoffreyanderson.net</xd:p>
            <xd:p><xd:b>Website:</xd:b> http://geoffreyanderson.net</xd:p>

    <xsl:variable name="newline">
    <xsl:template match="/">
        <xsl:for-each select="/w:comments/w:comment">
# Comment #<xsl:number value="position()" format="1"/> #
<xsl:for-each select="w:p">
<xsl:value-of select="$newline" />
<xsl:for-each select="w:r">
<xsl:value-of select="w:t"/>



The bad indenting is intentional so that you get output without weird tabbing/formatting. To use this (under Ubuntu, at least) simply unzip the DOCX file:

$ unzip someWordDoc.docx -d someWordDocDir/

And run the above XSL against the comments.xml file under the “word” directory:

$ xsltproc convertDocxCommentsToPlainText.xsl someWordDocDir/word/comments.xml

By doing this, you’ll get output similar to the following:

# Comment #1   #

        text of the first comment


# Comment #2   #

        text of the second comment



Posted in computing, latex, linux, programming, xml, xsl Tagged with: , , , ,