Becoming a creator, my website experience
Over the past few months, I have debated starting a new blog to discuss our ALS journey. I realized we were writing about ALS on the Data on Wheels...
2025-11-08
16 reads
Over the past few months, I have debated starting a new blog to discuss our ALS journey. I realized we were writing about ALS on the Data on Wheels...
2025-11-08
16 reads
I needed to test a striped backup, so I decided to ask the AI’s for help. This is part of a series of experiments with AI systems. The Problem...
2025-11-07 (first published: 2025-10-22)
259 reads
This is from 2010, but I loved that people felt this way about Redgate Software. A lot of these words are things that we aim to express to each...
2025-11-07
18 reads
In SQL Server environments where transactional replication runs alongside Always On Availability Groups (AGs), DBAs sometimes face a frustrating scenario: replication stalls when a secondary replica or subscriber is...
2025-11-07 (first published: 2025-10-21)
512 reads
It’s that time of the month again, and once again, I’m late and I’m hosting. I was traveling a lot in October and didn’t sort out hosting for this...
2025-11-07
31 reads
Today I’m in San Francisco at Small Data SF 2025. I went to the conference last year and thought it was a great event. Watching people talk about data...
2025-11-05
13 reads
For decades, enterprises have thought about data like plumbers think about water: you build pipelines, connect sources to sinks, and hope the pipes do not burst under pressure. That...
2025-11-05 (first published: 2025-10-17)
447 reads
Why you should connect resiliently to SQL Server
Transient failures happen — in the cloud (Azure SQL) and on-prem. A resilient connection strategy lets your app recover gracefully instead of...
2025-11-05 (first published: 2025-10-13)
397 reads
Welcome back, my fellow sleuths, to my mystery-inspired blog series! I’m having a ton of fun writing these, and I hope you’re enjoying the ride through SQL Server’s haunted...
2025-11-03 (first published: 2025-10-17)
300 reads
Don’t Let Trouble Sneak Up on You Most SQL Servers run quietly. Until they don’t. By the time someone notices an application outage or a failed backup, you’re...
2025-11-03 (first published: 2025-10-15)
330 reads
By HeyMo0sh
As a DevOps person, I know that to make FinOps successful, you need more...
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
Comments posted to this topic are about the item Restoring On Top II
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Comments posted to this topic are about the item Breaking Down Your Work
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers