<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Storage on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</title>
    <link>https://ronaldbradford.com/tags/storage/</link>
    <description>Recent content in Storage on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 01 Apr 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://ronaldbradford.com/tags/storage/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>An Interesting Artifact with AWS RDS Aurora Storage</title>
      <link>https://ronaldbradford.com/blog/interesting-artifact-with-aws-rds-aurora-storage-2025-04-01/</link>
      <pubDate>Tue, 01 Apr 2025 00:00:00 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/interesting-artifact-with-aws-rds-aurora-storage-2025-04-01/</guid>
      <description>As part of using public datasets with my own Benchmarking Suite I wanted upsize a dataset for larger volume testing.&#xA;I have always used the INFORMATION_SCHEMA.TABLES data_length and index_length columns as a sufficiently accurate measurement for actual disk space used.</description>
    </item>
  </channel>
</rss>
