SQL Bloggers – Join The PASS Blogger Group on LinkedIn
We launched this last week, a dedicated sub group for sql bloggers. To be eligible to join you have to...
2009-08-03
250 reads
We launched this last week, a dedicated sub group for sql bloggers. To be eligible to join you have to...
2009-08-03
250 reads
At 5:00 AM on August 1, 2009 I was awaken by a ringing cell phone. It was Mark, the official...
2009-08-03
491 reads
After a long weekend of travel and speaking, I’m finally able to put my feet up and get a little...
2009-08-03
997 reads
PASS is relaunching the SQL Server Standard with a wholly new approach and format. I’ll put more out about it...
2009-08-03
718 reads
I caught this blog post, Who says technical presentations can't be engaging?, today thanks to Dana Coffey (@crazeegeekchick on Twitter). ...
2009-08-03
336 reads
In reviewing database development best practices recently I'm reminded of an attitude I've found prevalent in many development shops, that...
2009-08-03
401 reads
Its very difficult to write what all new in Sql server 2005, almost everything is new... the complete engine has...
2009-08-03
731 reads
Its been fun and fulfilling getting neck deep into the Central Texas Capitol Area Users of SQL Server again after...
2009-08-02
501 reads
I’ve done all the testing I can do for now. There were some unexpected developments that I will cover in...
2009-08-02
557 reads
One of the interesting features of LinkedIn is the ability to post a reference about a connection. If you think...
2009-08-02
877 reads
By Steve Jones
I recently started playing with the MCP Server for SQL Server, which is a...
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...
Has anyone written a wrapper function (or similar) around STRING_AGG() to allow the retrieval...
Putting this here as we're currently on SQL Server 2019 installed on Windows Server...
Comments posted to this topic are about the item Never is Not the Policy
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_CustomerPhone
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.CustomerContact rebuildAfter I do this, what will I see for the index status? See possible answers