This year I have been speaking with an increasing number of people about FinOps and what it means. Fundamentally, it is all about getting a handle on the cost for our technology spend. When we step back and look at the bigger picture it also has ramifications on corporate Environmental, Social, and Governance (ESG) programs […]
2025-11-29
139 reads
2025-11-28
70 reads
Getting something done is important, but so is the quality level. Steve has a few thoughts today.
2025-11-26
100 reads
Today Steve tasks data modeling and wonders how many people still build and maintain models.
2025-11-24
133 reads
I'm writing this while in hiding at the PASS Data Community Summit that's taking place in Seattle this week. I just had a real surprise, finding out that DocumentDB is PostgreSQL under the covers and always has been. However, as much as I enjoy talking PostgreSQL, for the moment, I'll shut up about it. Instead, […]
2025-11-22
74 reads
2025-11-21
153 reads
Today we have a guest editorial reminding us that business knowledge is important, and we could all use some training.
2025-11-19
138 reads
AI can help us do more, but do we need to do more? Or more importantly, are we doing a good job of producing more useful stuff?
2025-11-17
190 reads
2025-11-15
104 reads
Do you take the time to model and design your database? Steve thinks this is important, even while trying to make changes quicker to adapt to changing requirements.
2025-11-14
103 reads
By Steve Jones
It’s Prime Day. A few of my recommendations, since I want to do some...
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
If you’ve been watching AI roll through the data community and thinking, “this seems...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Comments posted to this topic are about the item Concurrency and Baseline Control: Level...
Comments posted to this topic are about the item Spending Time in the Office
I have this code on SQL Server 2022. What happens when it runs all at once?
DROP TABLE IF EXISTS dbo.Commission GO CREATE TABLE dbo.Commission (id INT NOT NULL IDENTITY(1,1) CONSTRAINT CommissionPK PRIMARY KEY , salesperson VARCHAR(20) , commission VARCHAR(20) ) GO INSERT dbo.Commission ( salesperson, commission) VALUES ( 'Brian', 12 ), ( 'Brian', 'None' ) GOSee possible answers