Feature (In)Complete
A look at some of the interesting database news from the previous week (March 24, 2008).
2008-03-24
211 reads
A look at some of the interesting database news from the previous week (March 24, 2008).
2008-03-24
211 reads
As humans we look to share with each other, but there are times that this can be a bad thing. Steve Jones has a poll asking you about your sharing habits.
2008-03-21
95 reads
How often do you have those fire drills, testing what you would do in the event of an emergency. Would you be satisfied with a 30% success rate?
2008-03-19
110 reads
An idea that could save time and resources for backup and recovery in SQL Server.
2008-03-18
400 reads
SQL Server isn’t used much for web-based applications, simply because the cheapest ISPs use Linux and Apache for their platform. There are ISPs that provide a .NET platform and SQL Server but it is at a cost. SSDS seems to be Microsoft’s latest attempt to break into the market for database-driven websites.
2008-03-17
165 reads
2008-03-17
253 reads
2008-03-16
45 reads
2008-03-14
137 reads
Scaling out is hard to do with SQL Server, but why doesn't Microsoft build a better solution?
2008-03-13
295 reads
How much of a contract for servicing SQL Server should we expect? Has Microsoft broken an implied contract with us?
2008-03-11
99 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