2015-01-23 (first published: 2013-10-08)
30,015 reads
2015-01-23 (first published: 2013-10-08)
30,015 reads
Ever need to automatically stop a long running job? Ever need to find which named Schedule is the currently running version of your job? There's simple code that'll let you find out.
2013-04-25
6,192 reads
In part II of this series, Sioban Krzywicki shows us another way Tally Tables have helped solve problems - Text Parsing.
2010-08-03
9,438 reads
In the first part of a series on Tally Tables, Sioban Krzywicki shows how a Tally Table has helped out with fiscal year calculations.
2010-08-02
16,525 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