Ad Hoc SQL Server Help
I just need a few hours of your time… We get a variation of this request a LOT. So now it’s time to do something about it! Ad Hoc...
2026-03-02
10 reads
Kevin3NF
- Interests: Cycling, family, sci-fi, DBA stuff
SQL Server Upgrades: In-Place or New Server?
This isn’t a religious debate. I have a client right now debating how to handle SQL Server upgrades across all of their dev and test environments. And it’s...
2026-02-18 (first published: 2025-12-31)
414 reads
Data Conferences – Worth Every Dollar
Some of the best career enhancers you can buy. Why I Go to Conferences I go for two big reasons: Learning from the best. The folks teaching at...
2025-12-01 (first published: 2025-11-12)
277 reads
SQL Server Reliability: Clearing the Fuzzy Thinking
The terminology around reliability is a mess If you’ve ever said, “We’re covered, it’s replicated,” you’re in good company. SQL Server is a massive, 35+ year-old product that...
2025-11-19
16 reads
SQL Server Alerts
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
SQL Server Versions: Out With the Old, In With the Supported
If your production SQL Servers are still running 2016 (or older) you’re basically banking on inertia. Sure, it’s been stable. But that doesn’t guarantee it’ll stay safe or compliant....
2025-10-29
27 reads
SQL Server is Slow, part 3 of 4
In parts 1 and 2 of this series, we’ve gathered info and done the triage just like anyone in almost any industry does At this point you’ve: Defined what...
2025-10-27 (first published: 2025-10-01)
1,731 reads
SQL Server Migration Overview
It’s Not Just Backup / Restore At some point every company faces it: the SQL Server that’s been quietly running for years is due for retirement. Maybe the hardware...
2025-10-22
16 reads
SQL Server Is Slow (part 1 of 4)
How should you respond when you get the dreaded Email/Slack/Text/DriveBy from someone yelling at you that SQL Server is slow? Stop. Don’t Open SSMS Yet. You’ve heard it...
2025-10-08 (first published: 2025-09-17)
414 reads
“SQL Server Is Slow” Part 4 of 4
Parts 1, 2 and 3 got you to the (SQL) engine room. Now we use community-trusted tools to find what’s going on, fix it safely, and hopefully keep it...
2025-10-07
189 reads
Blogs
Building the Team: Roles and Responsibilities in FinOps
By HeyMo0sh
In my experience, FinOps success has never been just about tools or dashboards. It...
Tooling for Success: The Best FinOps Tools and Technologies
By HeyMo0sh
As a DevOps person, I know that to make FinOps successful, you need more...
From Planning to Practice: Setting Up Your FinOps Framework
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
Forums
Restoring On Top II
Comments posted to this topic are about the item Restoring On Top II
SQL Art 2: St Patrick’s Day in SSMS (Shamrock + Pint + Pixel Text)
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Breaking Down Your Work
Comments posted to this topic are about the item Breaking Down Your Work
Question of the Day
Restoring On Top II
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