2025-03-26
1,779 reads
2025-03-26
1,779 reads
Steve has a few thoughts after the end of mainstream support for SQL Server 2019.
2025-03-26
1,574 reads
Often we find out about a problem reported by a customer after the incident has passed. This might be from a trouble ticket or even an email that we...
2025-03-24
153 reads
Should we build modern software as monoliths or microservices? Or something else? Steve has a few thoughts today.
2025-03-24
149 reads
2025-03-24
756 reads
The main thing is to keep the main thing the main thing. – from Excellent Advice for Living We can summarize this advice as focus on what’s important. I...
2025-03-21
23 reads
2025-03-21
430 reads
Code is vulnerable to supply chain attacks, which aren't something many of us think about.
2025-03-21
122 reads
We published an article recently at SQL Server Central on Tally Tables in Fabric from John Miner. In it he showed how this can be efficient. A day after...
2025-03-21 (first published: 2025-03-12)
6,976 reads
2025-03-19
555 reads
Redshift keeps its SYS_* monitoring views for seven days in cluster, which is fine...
By Steve Jones
I was updating my session for the Data API Builder (DAB) recently, mostly to...
I am excited to host T-SQL Tuesday for the first time. I want to...
Working with SQL Server can involve more than just writing queries. Understanding database design,...
Comments posted to this topic are about the item Measuring Productivity
Comments posted to this topic are about the item Importing Excel files into SQL...
I have 3 instances of a brand new long running query that are executing on a SQL Server 2025 instance. Query store is enabled. One of the queries is killed by the administrator, one is cancelled by the user. The other runs to completion. How many rows are in Query Store for this query?
See possible answers