<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Innodb_file_per_table on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</title>
    <link>https://ronaldbradford.com/tags/innodb_file_per_table/</link>
    <description>Recent content in Innodb_file_per_table on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 11 Feb 2011 15:32:19 +0000</lastBuildDate>
    <atom:link href="https://ronaldbradford.com/tags/innodb_file_per_table/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Leveraging the InnoDB Plugin</title>
      <link>https://ronaldbradford.com/blog/leveraging-the-innodb-plugin-2011-02-11/</link>
      <pubDate>Fri, 11 Feb 2011 15:32:19 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/leveraging-the-innodb-plugin-2011-02-11/</guid>
      <description>Beginning with MySQL 5.1 as an additional plugin and included by default in MySQL 5.5 the InnoDB plugin includes many performance improvements. To leverage the support of new file formats however a very important setting is necessary.</description>
    </item>
  </channel>
</rss>
