2005-06-30
1,624 reads
Disaster Recovery (DR)
The DBA Whoops
Ever do something to your SQL Server 2000 server and then realize you've just broken something major? Ever have a moment when you want to go "whoops", but really feel like crying ot running away? Steve Jones just had one of those and gives you a few things to think about when you deal with a situation like that.
2005-06-16
12,071 reads
2005-06-01
1,825 reads
Why bother with backup?
Backing up SQL Server data is like many of the things we do because we figure we need to. It is good for you, like eating a good diet and getting exercise. Unfortunately, folks are often about as successful with SQL Server backups as they are with diet and exercise.
This is the first in a series of articles covering SQL Server database backup. The series starts from the very basics of why database backup is important. The question of why to backup a database can inform many other decisions.
2005-05-09
2,411 reads
2005-04-08
2,110 reads
2005-03-07
1,398 reads
2004-12-22
1,723 reads
2004-12-08
1,742 reads
Worst Practice - Detailed Disaster Plans
Another in our series of things you should avoid at all costs. Seems silly at first, not having a detailed recovery plan for your SQL Server. Perhaps it is, but having dealt with any number of problems over the last few years, Steve Jones has some ideas why a detailed plan may not be the best thing to spend your time on.
2004-11-09
8,091 reads
Incident Response - Responding to an Incident
Part 2 of Steve Jones' Incident Response series that looks at how you should be prepared as well as what to do when disaster strikes. Part 1 established a basic framework and part 2 dives deeper into what you might need for the next virus, hardware failure, or hurricane :(.
2004-10-11
4,936 reads
Blogs
The flight recorder: Replaying what an AI agent did on my SQL Server
By Arun Sirpal
“What exactly did it do on my server?” is the first question a DBA...
Announcements from the Microsoft Fabric Community Conference — Barcelona 2026
By James Serra
Microsoft shared a broad set of Fabric, Power BI, and SQL updates at FabCon...
Au Revoir for now
By Steve Jones
No, I’m not quitting or retiring. Just going on vacation, but I leave tonight...
Forums
Let's Talk Certifications
Comments posted to this topic are about the item Let's Talk Certifications, which is...
The Hidden Security Risks of Role Combination in SSAS Tabular
Comments posted to this topic are about the item The Hidden Security Risks of...
The Empty Aggregate
Comments posted to this topic are about the item The Empty Aggregate
Question of the Day
The Empty Aggregate
I have this table in a SQL Server 2025 database:
CREATE TABLE [dbo].[CustomerOrder] ( [OrderID] [int] NULL, [CustomerID] [int] NULL, [total] [money] NULL ) ON [PRIMARY] GOWhat is returned from this code? (answers are for the sum and then the count)
SELECT SUM(total) AS sum,
COUNT(total) AS count
FROM dbo.CustomerOrder;
See possible answers