Uncategorized

SQLServerCentral Editorial

Learn From History

  • Editorial

I've just spent a week in the UK visiting the Redgate HQ with my fellow advocates. I'm really blessed to get to work with such a great bunch of people. A couple of the conversations we had stuck with me and I'd like to share them here. Sitting in the midst of Cambridge, Cambridgeshire, UK, […]

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(1)

You rated this post out of 5. Change rating

2026-08-15

213 reads

Stairway icons Database Deployments

Managing Changesets Over Time: Stairway to Reliable Database Deployments Level 6

  • Stairway Step

As database changesets accumulate over time, they gradually become more than deployment artifacts. This level explores how a well-organized changeset library evolves into a replayable representation of the database’s structural history, supporting not only reliable deployments but also reconstruction, auditing, and long-term maintainability. Through practical examples and a real-world case study, it shows why maintaining coherent Create and Rollback scripts continues to provide value long after a successful production deployment.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

You rated this post out of 5. Change rating

2026-08-05

695 reads

SQLServerCentral Editorial

VACATION!

  • Editorial

Yeah, I've got the Go-Go's running in my head because I'm going on vacation tomorrow (holiday for you UK types). I've been slogging through a really dense book, War in Human Civilization. Total recommendation. Get it. Read it. However, I'm right near the end and there's been a lot of discussion about the impact of […]

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

You rated this post out of 5. Change rating

2026-08-01

167 reads

SQLServerCentral Editorial

AI Observability Challenges in FinOps as a DBA

  • Editorial

I was performing research for requested AI work and noticed that I was viewing the risks from a database perspective.  As the saying goes in the tech industry, “Once a DBA always a DBA…”  As foreign as some of the views were, much of it feels familiar and I simply begin to look at it […]

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(1)

You rated this post out of 5. Change rating

2026-07-25

153 reads

External Article

Pros and Cons of Database Sharding for Performance and Maintenance

  • Article

Large databases usually have a negative impact on maintenance time, scalability and query performance. For maintenance, these large single databases have to be backed up daily while the amount of actual changing data might be small. For performance, tables without correct indexes result in full table or clustered index scans. As the data grows the total query time increase linearly. How can we decrease downtime for the maintenance window for large databases and optimize the performance of daily queries?

2026-07-20

Blogs

T-SQL Tuesday #203: Risk and Reward

By

This is timely, as I’m currently on a boat in the Adriatic taking a...

dataMinds Connect 2026 – Slides & Scripts

By

You can find the slides and SQL scripts for my session “Spice up your...

How to Clear the SSMS Cache (SSMS 21 and Later)

By

How to Clear the SSMS Cache (SSMS 21 and Later) Updated...

Read the latest Blogs

Forums

Risk Vs Reward, The never ending ROI discussion.

By Pat Wright

Comments posted to this topic are about the item Risk Vs Reward, The never...

I Struggle

By Grant Fritchey

Comments posted to this topic are about the item I Struggle

Hyperscale Replicas IV

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Hyperscale Replicas IV

Visit the forum

Question of the Day

Hyperscale Replicas IV

In Azure SQL Database Hyperscale Edition, how many geo-replicas can be created?

See possible answers