<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Automation on Andy M Mallon - AM²</title><link>https://am2.co/tag/automation/</link><description>Recent content in Automation on Andy M Mallon - AM²</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 17 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://am2.co/tag/automation/index.xml" rel="self" type="application/rss+xml"/><item><title>Part 3: The hard part of a website migration</title><link>https://am2.co/2026/11/using-an-ai-agent-to-rebuild-a-website/</link><pubDate>Tue, 17 Nov 2026 00:00:00 +0000</pubDate><guid>https://am2.co/2026/11/using-an-ai-agent-to-rebuild-a-website/</guid><description>&lt;p&gt;The go-live was genuinely pretty boring.&lt;/p&gt;&#10;&lt;p&gt;We know what a compliment that is. I do enough incident response as part of my job &amp;ndash; I don&amp;rsquo;t need to do it in my free time as well.&lt;/p&gt;&#10;&lt;p&gt;In &lt;a href="https://am2.co/2026/11/03/cookin-up-website/"&gt;the first post&lt;/a&gt;, we assembled the replacement website as a copy of the real-life WordPress site. &lt;a href="https://am2.co/2026/11/10/moving-a-blog-without-breaking-the-content/"&gt;Last week&lt;/a&gt;, we dug through all the posts to fix what broke in the migration. Like IT pros, the new website was up and running and ready for traffic, just waiting to be switched over when the time was right.&lt;/p&gt;</description></item><item><title>Moving a blog without breaking the content</title><link>https://am2.co/2026/11/10/moving-a-blog-without-breaking-the-content/</link><pubDate>Tue, 10 Nov 2026 00:00:00 +0000</pubDate><guid>https://am2.co/2026/11/10/moving-a-blog-without-breaking-the-content/</guid><description>&lt;p&gt;&lt;a href="https://am2.co/2026/11/03/cookin-up-website/"&gt;Last week&lt;/a&gt;, &lt;span class="robot-cody"&gt;🤖Cody&lt;/span&gt;&#10; and I got the replacement website assembled and connected to Cloudflare. It looked like my blog. It had my posts. On the surface it looked good, but it needed a lot of attention to detail.&lt;/p&gt;&#10;&lt;h2 id="all-the-rows-are-there"&gt;All the rows are there&lt;/h2&gt;&#10;&lt;p&gt;The data was there, but if you recall, I am moving the site from WordPress (which uses HTML-based formatting) to Hugo (which uses Markdown-based formatting).&lt;/p&gt;</description></item><item><title>Stop using sp_hexadecimal &amp; sp_help_revlogin</title><link>https://am2.co/2021/07/dba-serverlogins/</link><pubDate>Tue, 06 Jul 2021 09:00:52 -0400</pubDate><guid>https://am2.co/2021/07/dba-serverlogins/</guid><description>&lt;p&gt;Since &lt;a class="tweet-ref" href="https://am2.co/2021/07/dba-serverlogins/#tweet-1384126645053771780" data-tweet-id="1384126645053771780"&gt;I started at Stack Overflow&lt;span class="visually-hidden"&gt; (read archived tweet)&lt;/span&gt;&lt;/a&gt;&#10;, I&amp;rsquo;ve had the chance to see some of the interesting challenges with running our databases at our scale.&lt;/p&gt;&#10;&lt;p&gt;My coworker Taryn Pratt (&lt;a href="https://tarynpivots.com/" rel="noopener" target="_blank"&gt;blog&lt;/a&gt;) recently blogged about &lt;a href="https://www.tarynpivots.com/post/2021/fighting-with-deadlocks/" rel="noopener" target="_blank"&gt;fighting with deadlocks&lt;/a&gt; related to &lt;a href="https://stackoverflow.com/teams/" rel="noopener" target="_blank"&gt;Stack Overflow for Teams&lt;/a&gt;.&lt;/p&gt;&#10;&lt;h2 id="lots-of-logins"&gt;Lots of logins&lt;/h2&gt;&#10;&lt;p&gt;Taryn mentions in her post that each team gets their own login, user, schema, etc. This means we have a lot of logins. Additionally, we use Availability Groups for our High Availability, which means we need to keep those logins in sync across AG Replicas.&lt;/p&gt;</description></item><item><title>Code to purge data based on creation date</title><link>https://am2.co/2019/04/code-to-purge-data-on-creation-date/</link><pubDate>Thu, 04 Apr 2019 08:30:16 -0400</pubDate><guid>https://am2.co/2019/04/code-to-purge-data-on-creation-date/</guid><description>&lt;p&gt;Yesterday, &lt;a href="https://am2.co/2019/04/03/purging-data-with-batched-deletes/"&gt;I talked about batching deletes&lt;/a&gt;, and the day before I talked about &lt;a href="https://am2.co/2019/04/02/the-thrill-of-purging-old-data/"&gt;how much I like to delete data&lt;/a&gt;, and why it&amp;rsquo;s necessary to do it, despite being a data packrat.&lt;/p&gt;&#10;&lt;p&gt;Today, let&amp;rsquo;s look at just one scenario, and how I like to handle it. In my experience, this is one of the most common purge requirements (and probably the easiest), so first, let&amp;rsquo;s look at the business requirements.&lt;/p&gt;</description></item><item><title>Purging data with batched deletes</title><link>https://am2.co/2019/04/purging-data-with-batched-deletes/</link><pubDate>Wed, 03 Apr 2019 08:30:13 -0400</pubDate><guid>https://am2.co/2019/04/purging-data-with-batched-deletes/</guid><description>&lt;p&gt;Yesterday, I wrote about &lt;a href="https://am2.co/2019/04/02/the-thrill-of-purging-old-data/"&gt;the importance of planning your data purges&lt;/a&gt;. Today, let&amp;rsquo;s look at the simplest requirement for purging data: Keep data for X days after it&amp;rsquo;s created. There are &lt;strong&gt;tons&lt;/strong&gt; of cases where this is the rule. Log data, telemetry data, even transactional data is often retained based on X days since it is created.&lt;/p&gt;</description></item><item><title>The thrill of purging old data</title><link>https://am2.co/2019/04/the-thrill-of-purging-old-data/</link><pubDate>Tue, 02 Apr 2019 09:00:54 -0400</pubDate><guid>https://am2.co/2019/04/the-thrill-of-purging-old-data/</guid><description>&lt;p&gt;DBAs &amp;amp; Data professionals tend to be digital pack rats. My personal Google Drive is filled with random files that I refused to part with&amp;ndash;even though it&amp;rsquo;s of questionable value. I lament that I do not have a copy of every paper I typed in high school or college&amp;ndash;and I envy those who do. You never know when you&amp;rsquo;ll need notes from that meeting 6 years ago, or when you&amp;rsquo;ll need that funny GIF you created for an inside joke you no longer remember.&lt;/p&gt;</description></item><item><title>Building a Twitter-bot RSS Aggregator</title><link>https://am2.co/2017/01/building-twitter-bot-rss-aggregator/</link><pubDate>Wed, 11 Jan 2017 23:13:34 -0500</pubDate><guid>https://am2.co/2017/01/building-twitter-bot-rss-aggregator/</guid><description>&lt;h2 id="i-hate-rssreaders"&gt;I hate RSS readers&lt;/h2&gt;&#10;&lt;p&gt;For some reason, about once a year, I go hunting for a new RSS reader so I can keep track of blogs that I like to read.  It&amp;rsquo;s always the same process:&lt;/p&gt;&#10;&lt;ol&gt;&#10;&lt;li&gt;Dig through reviews to find an app that I think I will love.&lt;/li&gt;&#10;&lt;li&gt;Come up with a list of blogs that I like to read.&lt;/li&gt;&#10;&lt;li&gt;Install and configure RSS reader app.&lt;/li&gt;&#10;&lt;li&gt;Spend the night reading blog posts.&lt;/li&gt;&#10;&lt;li&gt;Use app for a week.&lt;/li&gt;&#10;&lt;li&gt;Never open RSS reader app again.&lt;/li&gt;&#10;&lt;/ol&gt;&#10;&lt;p&gt;Well, it&amp;rsquo;s time to &lt;a href="https://www.youtube.com/watch?v=ZjfB4qDx3RM" target="_blank" rel="noopener noreferrer"&gt;stop the insanity&lt;/a&gt;. Its time to stop doing the same thing over and over again, hoping it will work this time. Its time to find a solution that really works.&lt;/p&gt;</description></item></channel></rss>