Editorials

SQLServerCentral Editorial

Shadow AI Data Leak Risk or “From the Desk of I saw that Coming”

CSO recently published an article based on a report from Harmonic about generative AI data leaks, and the findings were eye-opening. According to the report, over 8% of employee prompts to public large language models (LLMs) contained sensitive data, ranging from security and compliance issues to privacy and legal vulnerabilities. This wasn’t just a handful […]

(1)

You rated this post out of 5. Change rating

2025-03-08

159 reads

SQLServerCentral Editorial

What is time?

There was a post on X I read today about valuing your time. The gist was that since this person had waited 9 minutes to save $4, they valued their time at $27 an hour. I get the point being made. Time is valuable and you need to set the value of your time. It […]

You rated this post out of 5. Change rating

2025-03-01

99 reads

Blogs

Accessing the Data API Builder MCP Server from VS Code

By

I recently started playing with the MCP Server for SQL Server, which is a...

From DBA or Data Engineer to AI Engineer: A Realistic Path

By

If you spend your days tuning queries, managing pipelines, or keeping a production database...

Asynchronous Replication of Snapshots from an ActiveCluster Pod to a Third Array

By

I’ve been rebuilding my three-site SQL Server demo lab, and I ran into something...

Read the latest Blogs

Forums

STRING_AGG DISTINCT

By Phil Parkin

Has anyone written a wrapper function (or similar) around STRING_AGG() to allow the retrieval...

In-place OS upgrade or migration to new OS?

By jasona.work

Putting this here as we're currently on SQL Server 2019 installed on Windows Server...

Never is Not the Policy

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Never is Not the Policy

Visit the forum

Question of the Day

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_CustomerPhone
ON dbo.CustomerContact (phone);
I then do this to disable one index:
alter index IX_CustomerContact_CustomerPhone on dbo.CustomerContact disable
I see this when I check the index status:Index status for CustomerContactI decide to rebuild all indexes with this command:
ALTER INDEX ALL ON dbo.CustomerContact rebuild
After I do this, what will I see for the index status?

See possible answers