December 2011 LV UG Meeting
The Holidays are upon us. It is time to take a break from the hustle and bustle and come out to participate in the local User Group for SQL...
2011-11-30
10 reads
The Holidays are upon us. It is time to take a break from the hustle and bustle and come out to participate in the local User Group for SQL...
2011-11-30
10 reads
The Holidays are upon us. It is time to take a break from the hustle and bustle and come out...
2011-11-30
1,629 reads
As I did for powershell a day Series Blog April 2011, consolidated the all months blog into one pdf file here....
2011-11-30
1,432 reads
My main phone line at the house has been on the fritz for about 3-4 weeks. Yes, we still have...
2011-11-30
2,432 reads
I have lost an hour today trying to find a bug in my SSIS package, and it was so small...
2011-11-30
6,828 reads
With the announcement of the official slate for the BoD election for this year, the job of the NomCom is...
2011-11-30
2,551 reads
Here is the list of suckers, uh, I mean, candidates, that actually want to subject themselves to the board. Look...
2011-11-30
2,327 reads
There is nothing like having two children to remind you how strange, funny, and complicated language can be. Try answering...
2011-11-30
1,600 reads
Want 2 days of Microsoft SQL Server training where you can hand-pick what you're learning about for the low price...
2011-11-30
2,040 reads
The Professional Association for SQL Server and the North Texas SQL Server User Group have been working hard behind the...
2011-11-30
1,489 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