2016-04-05
9 reads
2016-04-05
9 reads
2016-04-05
5 reads
2015-10-19
8 reads
2015-10-19
6 reads
2015-10-19
14 reads
Detecting worst performing queries executed in a particular duration and how many times it got executed and fine tuning them is a single most efficient technique to fix unexpected...
2015-10-19
12 reads
Detecting worst performing queries executed in a particular duration and how many times it got executed and fine tuning them...
2015-10-19
834 reads
on 10th oct 01.30 pm pst, i will be speaking on “detect worst performing sql queries during peak hour” @ sqlsaturday,...
2015-10-05
779 reads
2015-10-05
11 reads
2015-10-05
4 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