<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Locking on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</title>
    <link>https://ronaldbradford.com/tags/locking/</link>
    <description>Recent content in Locking on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 17 Nov 2010 11:00:09 +0000</lastBuildDate>
    <atom:link href="https://ronaldbradford.com/tags/locking/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Casual MySQL DBA – Operational Basics</title>
      <link>https://ronaldbradford.com/blog/the-casual-mysql-dba-operational-basics-2010-11-17/</link>
      <pubDate>Wed, 17 Nov 2010 11:00:09 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/the-casual-mysql-dba-operational-basics-2010-11-17/</guid>
      <description>So your not a MySQL DBA, but you have to perform like one. If you have a production environment that’s running now, what are the first things you do when it’s not running or reported as not running?</description>
    </item>
    <item>
      <title>Common MySQL Scalability Mistakes</title>
      <link>https://ronaldbradford.com/blog/common-mysql-scalability-mistakes-2010-10-02/</link>
      <pubDate>Sun, 03 Oct 2010 03:32:37 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/common-mysql-scalability-mistakes-2010-10-02/</guid>
      <description>This week I was one of the presenters at the first Surge Scalability Conference in Baltimore. An event that focused not just on one technology but on what essential tools, technologies and practices system architects need to know about for successfully scaling web applications.</description>
    </item>
    <item>
      <title>Understanding Innodb Transaction Isolation</title>
      <link>https://ronaldbradford.com/blog/understanding-mysql-innodb-transaction-isolation-2009-09-24/</link>
      <pubDate>Thu, 24 Sep 2009 06:33:04 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/understanding-mysql-innodb-transaction-isolation-2009-09-24/</guid>
      <description>The MySQL Innodb storage engine provides ACID compliance, the ‘I’ being isolation. There are four states defined in MySQL with the tx_isolation system variable, READ-UNCOMMITTED, READ-COMMITTED, REPEATABLE-READ and SERIALIZABLE.&#xA;Generally MySQL installations do not modify the default value of tx_isolation = REPEATABLE-READ, however I have seen with a number of clients the default value has been changed to READ-COMMITTED.</description>
    </item>
    <item>
      <title>Understanding InnoDB MVCC</title>
      <link>https://ronaldbradford.com/blog/understanding-innodb-mvcc-2009-07-15/</link>
      <pubDate>Wed, 15 Jul 2009 04:24:56 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/understanding-innodb-mvcc-2009-07-15/</guid>
      <description>Multi versioning concurrency control (MVCC) is a database design theory that enables relational databases to support concurrency, or more simply multiple user access to common data in your database.&#xA;In MySQL the InnoDB storage engine provides MVCC, row-level locking, full ACID compliance as well as other features.</description>
    </item>
  </channel>
</rss>
