<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Next BaseLine on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</title>
    <link>https://ronaldbradford.com/categories/next-baseline/</link>
    <description>Recent content in Next BaseLine on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 09 Nov 2024 22:07:38 +0000</lastBuildDate>
    <atom:link href="https://ronaldbradford.com/categories/next-baseline/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Managing SQL Drift: Ensuring Stability in Database Transitions</title>
      <link>https://ronaldbradford.com/blog/managing-sql-drift-ensuring-stability-in-database-transitions-2024-11-09/</link>
      <pubDate>Sat, 09 Nov 2024 22:07:38 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/managing-sql-drift-ensuring-stability-in-database-transitions-2024-11-09/</guid>
      <description>SQL drift is a significant challenge that occurs when SQL statements from an existing system produce unexpected results after migration to a new environment or system. These issues manifest in several critical ways: SQL statements may generate new execution errors, experience significant performance degradation, or yield differences in data integrity.</description>
    </item>
    <item>
      <title>Database testing for all version changes  (including minor versions)</title>
      <link>https://ronaldbradford.com/blog/database-testing-for-all-version-changes-including-minor-versions-2024-06-19/</link>
      <pubDate>Wed, 19 Jun 2024 15:54:01 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/database-testing-for-all-version-changes-including-minor-versions-2024-06-19/</guid>
      <description>We know that SQL statement compatibility can change with major database version upgrades and that you should adequately test for them. But what about minor version upgrades?&#xA;It is dangerous to assume that your existing SQL statements work with a minor update, especially when using an augmented version of an open-source database such as a cloud provider that may not be as transparent about all changes.</description>
    </item>
    <item>
      <title>The curse of MySQL warnings</title>
      <link>https://ronaldbradford.com/blog/the-curse-of-mysql-warnings-2024-06-10/</link>
      <pubDate>Mon, 10 Jun 2024 20:29:00 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/the-curse-of-mysql-warnings-2024-06-10/</guid>
      <description>MySQL warnings are an anti-pattern when it comes to maintaining data integrity. When the information retrieved from a database does not match what was entered, and this is not identified immediately, this can be permanently lost.</description>
    </item>
  </channel>
</rss>
