T-SQL Tuesday Retrospective #012: Why DBA skills are necessary
This is my ongoing series of answering T-SQL Tuesday posts far too late to be of any use. Click here if you want to read previous entries. Paul Randal...
2021-03-17
141 reads
This is my ongoing series of answering T-SQL Tuesday posts far too late to be of any use. Click here if you want to read previous entries. Paul Randal...
2021-03-17
141 reads
(If you would like to read the previous T-SQL Tuesday Retrospective entries, visit this link.) In October 2010, Sankar Reddy asked us which misconceptions we’ve been labouring under when...
2021-03-16 (first published: 2021-03-10)
313 reads
SQL Server is a complex beast, with many configuration options that can range from recommended to completely avoided. Since the release of SQL Server 2016, several options that were...
2021-03-03
66 reads
After the Professional Association of SQL Server (PASS) unceremoniously closed down in January this year and its video library & brand names were bought by Red Gate Software Ltd, it...
2021-02-24
102 reads
This Wednesday, from 5pm to 7pm Mountain Standard Time, the Calgary Data User Group is presenting two sessions for your virtual attendance. 15 minutes: A lightning talk on Kubernetes...
2021-02-22
30 reads
(Thanks to Erik Darling for reviewing this post. Check out his training materials.) One of the bigger clichés in the data professional vocabulary (behind “it depends”) is that you...
2021-04-20 (first published: 2021-02-17)
547 reads
Some years ago, I wrote about what it means to be “professional” (and that it doesn’t mean having to wear a suit and tie). Recently a conversation broke out...
2021-02-10
182 reads
(You can see previous T-SQL Tuesday retrospectives by visiting this link.) In September 2010, Michael J. Swart (blog | Twitter) invited us to talk about indexes. Indexes are strange...
2021-02-03
30 reads
(If you’d like to read my other T-SQL Tuesday Retrospective posts, click here.) In August 2010, Jason Brimhall (blog | Twitter) invited us to discuss preparing for vacations: “Write...
2021-01-27
17 reads
If you’re reading this, there’s a good chance you’re straight, white, male, and English-speaking. There’s also a high likelihood that you live in the United States. The technology industry...
2021-01-20
36 reads
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...
By SQLPals
SQL Server gMSA: Why DBAs Still Aren't Using It in 2026 ...
Comments posted to this topic are about the item Never is Not the Policy
Comments posted to this topic are about the item Automating SSAS Multidimensional Security Audits...
Comments posted to this topic are about the item 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