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.
DBAs & Data professionals tend to be digital packrats. My personal Google Drive is filled with random files that I refused to part with–even though it’s of questionable value. I lament that I do not have a copy of every paper I typed in high school or college–and I envy those who do. You never know when you’ll need notes from that meeting 6 years ago, or when you’ll need that funny GIF you created for an inside joke you no longer remember.
I’m a college drop-out. When I was trying to figure out my life, a friend (my brother’s ex) referred me to a software company where she was working–I got the job because I was (a) breathing, (b) eager to do the job, and (c) cheap. … [Read More]
Bloggers spend a lot of time writing about our successes, but we’re human and we make mistakes, too. This post is a chance to share one of my memorable failures.
I was recently fussing with a CSV file that had an inconsistent number of columns. UGH. There was a bunch of historical data that had 4 columns, and then more recent data had a new attribute added with 5 columns. I spent a few minutes … [Read More]
About two years ago, I moved my home office down into the basement at our house. Earlier this year, I started a new job at SentryOne, and work from home full time. This means I spend more (awake) time in my office than any other room in the house. I thought I’d take everyone through a guided tour of my home office.
Copyright © 2024 | Andy Mallon | am2.co