2008-02-27 (first published: 2008-01-21)
1,041 reads
2008-02-27 (first published: 2008-01-21)
1,041 reads
2008-02-25 (first published: 2008-01-15)
933 reads
These examples show how You can circumvent the problem with not working TOP 100 PERCENT and ORDER BY in views.
2008-02-22 (first published: 2008-01-22)
1,300 reads
2008-02-21 (first published: 2008-01-09)
2,007 reads
2008-02-18 (first published: 2007-12-27)
816 reads
2008-02-14 (first published: 2007-12-20)
1,040 reads
2008-02-13 (first published: 2007-12-18)
1,746 reads
Use this proc if you need to alter a column that is part of a primery key
2008-02-04 (first published: 2007-12-10)
1,126 reads
Sample solution to replace string in expressions with multiple delimiters.
2008-01-31 (first published: 2007-12-05)
2,001 reads
2008-01-29 (first published: 2007-11-23)
1,978 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