Most of Us Are Vulnerable
Security is hard, and while data professionals might not be responsible for network issues, we ought to be aware that there could be vulnerabilities that might attack our systems.
2022-01-19
251 reads
Editorials
It Isn't Worth Automating
Every year I'm responsible for a portion of the Database Weekly newsletters. I used to do half, but right now Kathi, Grant, and I are on a rotation. Our boss puts out a schedule each year, which tells me the weeks for which I am responsible. Each January I then set up a recurring appointment […]
2022-01-17
191 reads
T-SQL Requires the Right Approach
Some of the most problematic T-SQL code I’ve seen over the years originated because the developer approached T-SQL with techniques more suitable for developing applications. I often saw these issues in my consulting days and always took the opportunity to teach the customer instead of only fixing the problems. One reason is that SQL is […]
2022-01-15
224 reads
2022-01-14
310 reads
Coding for the Future
Writing code that solves problems and adapts to the future is a challenge, but it's something we should think about.
2022-01-12
280 reads
Teams Security Issues
There are a few security issues in the Teams application from Microsoft, and Steve notes that some of the push for new features can be a problem in this area.
2022-01-10
300 reads
Where the World Takes You
We're launching into a new year and there are lots of "looking into the future" articles out there. Personally, I'm pretty jazzed for the coming year for any number of reasons (can you say "SQL Server 2022"?). However, I also get a little retrospective at times like this. Now, I'm not going to talk about […]
2022-01-08
180 reads
What Were Your 2021 Wins
The first poll question of the year has Steve asking you to look back at 2021 and pick something good that happened.
2022-01-07
184 reads
Challenging Trends
Steve notes the changes in the world might affect how to view and use data in our work.
2022-01-05
281 reads
Data Cleanup
Steve wishes we could do some data cleanup and archival every year. Or even more often.
2022-01-03
328 reads
Blogs
When Your Microsoft Fabric Capacity Runs Out: Optimize, Scale Up, Scale Out, or Isolate?
By James Serra
Microsoft Fabric makes it wonderfully easy to put many analytics workloads on one platform....
Accessing the Data API Builder MCP Server from VS Code
By Steve Jones
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
If you spend your days tuning queries, managing pipelines, or keeping a production database...
Forums
STRING_AGG DISTINCT
Has anyone written a wrapper function (or similar) around STRING_AGG() to allow the retrieval...
In-place OS upgrade or migration to new OS?
Putting this here as we're currently on SQL Server 2019 installed on Windows Server...
Never is Not the Policy
Comments posted to this topic are about the item Never is Not the Policy
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 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