T-SQL Tuesday Retrospective #004: I/O
Mike Walsh invited us on March 1st 2010 to write about I/O. This abbreviation stands for Input / Output, and is often used as shorthand for persisted storage. Given...
2020-11-11
21 reads
Born SQL with Randolph West
The rule of three, SQL Server on Linux edition
When it comes to Microsoft products, the rule of three — at least as far as I’m concerned — is where you can accomplish the same task in three...
2020-11-10
81 reads
T-SQL Tuesday Retrospective #003: Relationships
In my quest to respond to every T-SQL Tuesday since the dawn of the end of 2009, it was only a matter of time before Rob Farley’s name came...
2020-11-04
30 reads
T-SQL Tuesday Retrospective #002: A Puzzling Situation
For the second T-SQL Tuesday ever — again, hosted by Adam Machanic — we were asked one of three options, and I elected to go with the first one:...
2020-11-02 (first published: 2020-10-28)
321 reads
The T-SQL Tuesday Corollary
T-SQL Tuesday is a fantastic series of blog posts derived from over 130 topics over the past 11 years, inviting bloggers to share their thoughts on a particular theme...
2020-10-21
26 reads
A more considered approach to email signatures
This — like last week’s post — is not about SQL Server or Azure SQL Database. In a way, it hearkens back to a post I wrote a few years...
2020-10-14
39 reads
Read the error message
This post is brought to you — indirectly — from a boss I loved working for, on a project which almost killed me, at a company which I had...
2020-10-07
443 reads
How SQL Server stores data types: sql_variant
This post looks at a curious data type that isn’t really a data type. Instead, sql_variant tries to be all things to all people. As with most things in...
2020-09-30
231 reads
A new malware attack on SQL Server
Tencent Security has released a report (written in Chinese) describing a new malware attack by the name of “MrbMiner” on SQL Server instances exposed to the Internet with passwords that can...
2020-09-23
389 reads
If not me, then who?
[Content Warning: this post contains references to subjects that may trigger a trauma response. Read with caution.] This is not a technical post. I was going to write about...
2020-09-16
56 reads
Blogs
From DBA or Data Engineer to AI Engineer: A Realistic Path
If you spend your days tuning queries, managing pipelines, or keeping a production database...
Asynchronous Replication of Snapshots from an ActiveCluster Pod to a Third Array
I’ve been rebuilding my three-site SQL Server demo lab, and I ran into something...
SQL Server gMSA: Why So Many DBAs Still Aren't Using It in 2026
By SQLPals
SQL Server gMSA: Why DBAs Still Aren't Using It in 2026 ...
Forums
Never is Not the Policy
Comments posted to this topic are about the item Never is Not the Policy
Automating SSAS Multidimensional Security Audits with PowerShell
Comments posted to this topic are about the item Automating SSAS Multidimensional Security Audits...
Rebuilding All Indexes
Comments posted to this topic are about the item Rebuilding All Indexes
Question of the Day
Rebuilding All Indexes
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_CustomerEmail
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.CustomerContactAfter I do this, what will I see for the index status? See possible answers