SQL Saturday #198, Vancouver, BC Session Files
This past weekend was SQL Saturday #198 in Vancouver, B.C. It started off with a leisurely drive up to Vancouver...
2013-02-19
1,255 reads
SQL Server Soldier :: News from the frontlines of the database wars
Day 28 of 31 Days of Disaster Recovery: Recovering SQL if the Tempdb Drive Dies
Welcome to day 28 of my series 31 Days of Disaster Recovery. Today I want to talk about recovering SQL...
2013-02-22 (first published: 2013-02-14)
2,894 reads
Day 27 of 31 Days of Disaster Recovery: Restoring Part of a Database
Today is day 27 of my series 31 Days of Disaster Recovery, and I want to talk about restoring a...
2013-02-12
1,104 reads
SQLSoldier World Tour Kicks Off in 1 Week
The SQLSoldier World Tour kicks off this next Friday when I head up to Vancouver, in British Columbia, Canada. I...
2013-02-10
1,098 reads
Day 26 of 31 Days of Disaster Recovery: The Mysterious Case of the Long Backup
Welcome back for day 26 of my series 31 Days of Disaster Recovery. Today I want to share a tale...
2013-02-10
1,125 reads
Day 25 of 31 Days of Disaster Recovery: Improving Performance of Backups and Restores
My series 31 Days of Disaster recovery has been on hiatus due mostly to illness. I’ve been battling a chest...
2013-02-10
1,300 reads
Day 24 of 31 Days of Disaster Recovery: Handling Corruption in a Clustered Index
Welcome to day 24 of my 31 Days of Disaster Recovery series. Previously, I’ve talked about several different forms of...
2013-01-31
1,856 reads
Day 23 of 31 Days of Disaster Recovery: Restoring Differential Backups With New Files
It’s day 23 of my 31 Days of Disaster Recovery series, and today’s blog post is inspired from an email...
2013-01-29
1,586 reads
Day 22 of 31 Days of Disaster Recovery: Which DBCC CHECK Commands Update Last Known Good DBCC
The end of the day is quickly approaching as I finish this blog post. This is day 22 in my...
2013-01-27
1,439 reads
Day 21 of 31 Days of Disaster Recovery: Who Deleted That Data?
Welcome back for day 21 of my 31 Days of Disaster Recovery series. Today I want to talk about trying...
2013-01-26
1,518 reads
Blogs
Keeping Redshift System Table History Past 7 Days with S3 Tables
Redshift keeps its SYS_* monitoring views for seven days in cluster, which is fine...
Updating the Data API Builder
By Steve Jones
I was updating my session for the Data API Builder (DAB) recently, mostly to...
T-SQL Tuesday #202 Invitation: That One SQL Server Outage You’ll Never Forget
I am excited to host T-SQL Tuesday for the first time. I want to...
Forums
Practical Ways to Approach SQL Server Problems and Case Studies
Working with SQL Server can involve more than just writing queries. Understanding database design,...
Measuring Productivity
Comments posted to this topic are about the item Measuring Productivity
Importing Excel files into SQL Server using DuckDB and Python
Comments posted to this topic are about the item Importing Excel files into SQL...
Question of the Day
Tracking All the Queries
I have 3 instances of a brand new long running query that are executing on a SQL Server 2025 instance. Query store is enabled. One of the queries is killed by the administrator, one is cancelled by the user. The other runs to completion. How many rows are in Query Store for this query?
See possible answers