In Year Three, I had a pretty big year. I kind of felt like I had peaked. I had received the Community Influencer of the Year Award and Microsoft MVP Award. Where do you go from there? Mostly, I just wanted to keep up what … [Read More]
In Year Three, my goal was to keep focused on what I learned in the FreeCon the year before, and keep moving forward with speaking and blogging. I was putting a bit more effort into my speaking (and thus easing off on the blogging some).
In Year 1, I only wrote 6 blog posts. In Year 2, I decided to take things seriously, and kicked things into high gear. During this 12-month period, I wrote 36 blog posts–my best 12-months as far as pace & productivity in these five years.
I’ve lost my blog stats for that first year, so I can’t say exactly how many visitors I had. I can say that the number of views was so low that it didn’t matter. If I were going to offer a generous estimate, I would guess I got whopping 100 page views in year one (mostly from me). I wrote a total of six blog posts that year. Let’s look at two of my favorites.
On May 16, 2014, I bought a domain on a whim. I’d been sitting in the NOCC at my employer, helping with maintenance. I was waiting on another team to perform their task, and champing at the bit. Over the next week, I set up a Blogger website, tied my domain to it, and thought about what I’d done at work recently that might be worth sharing.
Last night while having dinner with my husband, I had a thought and messaged Chrissy LeMaire (blog|twitter) on the SQL Server Community Slack. Thoughts on an LGBTQ channel here? I doubt it would be very active… But I’d love to have a spot for the … [Read More]
There’s a lot of discussion about preventing downtime. As a DBA and IT professional, it’s my sworn duty to prevent downtime. I usually describe my job as DBA something along the lines of, “to make sure data is always available to the people and applications … [Read More]
Starting with SQL Server 2017 CU6 and SQL Server 2016 SP2-CU3, you can now configure your distribution database as part of an Availability Group (AG). I found one spot where a minor change made a few of my scripts blow up.
Yesterday, I talked about batching deletes, and the day before I talked about how much I like to delete data, and why it’s necessary to do it, despite being a data pack rat. Today, let’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’s look at the business requirements.
Yesterday, I wrote about the importance of planning your data purges. Today, let’s look at the simplest requirement for purging data: Keep data for X days after it’s created.