DaveWentzel.com            All Things Data


The Accidental MySQL DBA

If you are an "accidental MySQL DBA" this post is for you.  I assume you know almost nothing about MySQL, or its derivatives...such as MariaDB and Percona.  This post will give you just enough to get up-to-speed quickly and will give you enough knowledge to perform information google searches to find more detailed information.  I assume you have a working knowledge of MS SQLServer and I'll compare and contrast the two.  


Linux Performance Management for the DBA

Sometimes a DBA doesn't have the luxury of a Linux administrator when help is needed diagnosing performance problems.  It doesn't matter if you are an accidental DBA for PostgreSQL, MySQL, Vertica, or any other database manager (NoSQL included)...you really should know how to detect if your OS is performing its best.  This post is a quick guide for a DBA (or anyone really) who needs to get up-to-speed quickly on Linux from a performance management perspective.  

Migrating gitlab to omnibus from source, debian to rpm, apache to nginx, and mysql to postgresql

I've had my own gitlab installation for a few years.  I built it long before it was easy to build and maintain.  Originally I installed gitlab from source, on ubuntu, using mysql and apache.  It's a real PITA to maintain given that omnibus installations are so much easier to maintain.  (omnibus is geek-speek for "all-in-one").  In this post I'll cover the steps I did to pull off upgrading this to omnibus, switching to postgresql from mysql, apache to nginx, and ubuntu to centos (which is my new Linux standard).  


Other MySQL Performance Management Tooling

In my last post, nodetitle, I covered the performance_schema which is a relatively new feature of MySQL 5.5.  If you are using an earlier version of MySQL you won't have access to performance_schema.  This post covers your alternatives when you find yourself facing a performance problem as an "accidental MySQL DBA".  

Introduction to the MySQL Performance Schema

If you are new to performance troubleshooting with MySQL, specifically using the performance_schema, then this post is for you.  If you are an "accidental DBA" for MySQL, and you need to quickly fix some performance problems, then read on.  This post will give you example queries and background to get your MySQL performance problems solved quickly.  

Storm Notes

Need to get up-to-speed quickly on the basics of Apache Storm?  This quick post will give you everything you need to know to speak somewhat competently about Storm.  You'll learn the general architecture, terms, proper use cases, and basic administration and performance management.  

Couchbase Notes

If you have 10 minutes this blog post will give you a quick overview of what Couchbase is, how it works, and some gotchas.  Couchbase is a document-oriented, key-value store that is very simplistic.  But it's also rock solid.  If you are evaluating document stores and you need to come up to speed quickly on Couchbase then this post is for you.  


Kafka Notes

I'm learning Apache Kafka which is a wicked-fast asynchronous messaging system used, generally, as a source spout for Apache Storm.  In general, in hadoop the loading/streaming data patterns use Kafka by producing a message to a Kafka "topic" and then consuming it later.  This post is just my notes on how to administer and troubleshoot Apache Kafka.  

Service Broker Demystified Series - Summary

This blog series focused on the common complaints I hear about SQL Server Service Broker...namely that it is too confusing for a data professional to master.  The fact that there is no (good) GUI or monitoring tools doesn't help either.  In this series I simplified things and explained why SSB works the way it does.  I also provided tricks and shortcuts to make everything a little simpler.  SSB is a really great technology and I find new uses for it almost every day.  

Service Broker Demystified - How to Radically Simplify SB

Setting up Service Broker objects can be challenging.  Objects need to be deployed in the correct dependency order.  And then if something goes wrong you need to determine what objects need to be recreated as well as what messages may still be "stalled" and waiting for processing.  In this post I'll show you my "pattern" script that helps to ease these burdens.  Using the concept of "script idempotency" I can guarantee that all objects are deployed and running correctly.  At any time.  


Subscribe to RSS - blogs