KDA: Echoes of Deception - Case 5
A deleted podcast episode, 17 million archive log entries, and KQL's time series analysis to find the backup that was never supposed to survive.
2026-06-25
15 reads
A deleted podcast episode, 17 million archive log entries, and KQL's time series analysis to find the backup that was never supposed to survive.
2026-06-25
15 reads
It’s Prime Day. A few of my recommendations, since I want to do some shopping myself (yes, these are commissioned referrals). These are things I’ve ordered and used this...
2026-06-24 (first published: 2026-06-23)
42 reads
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting build entirely in Fabric where you can have almost live data in reports. The pitch...
2026-07-08 (first published: 2026-06-23)
277 reads
If you’ve been watching AI roll through the data community and thinking, “this seems useful, but I have no idea where to start,” this post is for you.
The post...
2026-07-06 (first published: 2026-06-22)
367 reads
Not every production incident is a database in RECOVERY_PENDING or a corrupted event (like the other post). Sometimes the server is just a mess. Jobs failing. Error log full...
2026-06-23 (first published: 2026-06-22)
51 reads
It is Friday, the queries are running, and nobody is watching the bill. That is the whole charm of Redshift Serverless: you stop thinking about nodes and resizes. It...
2026-07-03 (first published: 2026-06-19)
254 reads
Annabel retired from Redgate Software this week. Across most of my career at Redgate, I’ve participated in many events, some we hosted, some we sponsored. At most of these...
2026-07-03 (first published: 2026-06-19)
251 reads
As a SQL Server DBA with years of experience tuning production environments, I’ve seen the same patterns repeat: nightly index maintenance jobs running for hours, consuming massive CPU and...
2026-07-06 (first published: 2026-06-19)
1,054 reads
Once again there were a number of Microsoft Build announcements related to data and AI, and some were very impressive. Below are my favorites. I am prioritizing the data...
2026-07-01 (first published: 2026-06-18)
433 reads
A good week ago I hosted the monthly T-SQL Tuesday blog party. I invited the community the blog about the idea of what would happen if we would need...
2026-06-19 (first published: 2026-06-18)
36 reads
By Steve Jones
I recently started playing with the MCP Server for SQL Server, which is a...
If you spend your days tuning queries, managing pipelines, or keeping a production database...
I’ve been rebuilding my three-site SQL Server demo lab, and I ran into something...
Has anyone written a wrapper function (or similar) around STRING_AGG() to allow the retrieval...
Putting this here as we're currently on SQL Server 2019 installed on Windows Server...
Comments posted to this topic are about the item Never is Not the Policy
I have added a few indexes to one of my tables in SQL Server 2025:
ALTER TABLE dbo.CustomerContact
ADD CONSTRAINT PK_CustomerContact
PRIMARY KEY (CustomerID);
-- Create index on CustomerEmail
CREATE INDEX IX_CustomerContact_CustomerEmail
ON dbo.CustomerContact (CustomerEmail);
CREATE INDEX IX_CustomerContact_CustomerPhone
ON dbo.CustomerContact (phone);
I then do this to disable one index:
alter index IX_CustomerContact_CustomerPhone on dbo.CustomerContact disableI see this when I check the index status:
I decide to rebuild all indexes with this command:
ALTER INDEX ALL ON dbo.CustomerContact rebuildAfter I do this, what will I see for the index status? See possible answers