So You Think You Should Get a Radio
This is not database related, so if you’re not interested in hearing about something besides SQL Server, PostgreSQL, DevOps, community or data management in general, time to move on....
2025-04-30
18 reads
This is not database related, so if you’re not interested in hearing about something besides SQL Server, PostgreSQL, DevOps, community or data management in general, time to move on....
2025-04-30
18 reads
Everything in SQL Server is waiting for something…this is by design. And most people never think about it… Until your application is waiting to complete its request, sell the...
2025-04-30 (first published: 2025-04-16)
378 reads
SQL Saturday Austin 2025 is in just a few days. I am honored to be speaking there, and glad to be going back. I’ve missed a number of the...
2025-04-29
47 reads
I’m excited to announce that on June 17 – 18, 2025, I’ll be running a special Online Live Training event focused entirely on SQL Server Query Tuning! This is...
2025-04-28
19 reads
I’ve been using the SSMS preview for v21. This is the next evolution of SSMS, where the VS shell is finally being updated. For many of us, SSMS has...
2025-04-28
99 reads
I’m sure I’ve never mentioned that I’m an amateur radio operator. Like Vegans and Cross Fitters, we tend to be shy and withdrawn about our predilections. BWA-HA-HA! Ok, like...
2025-04-28 (first published: 2025-04-11)
349 reads
This came up one day at my work when a developer was using it. I hadn’t used it before and thought I’d better check it out. It’s off by...
2025-04-28 (first published: 2025-04-11)
932 reads
While I mostly write about SQL Server, I have a soft spot for Kusto. In this series, I will explore solutions to fun challenges collectively known as the Kusto...
2025-04-27 (first published: 2025-04-26)
91 reads
In the bustling world of sports, leadership appears as a beacon of hope and direction. Imagine a football team, standing on the brink of a crucial match. The players,...
2025-04-25 (first published: 2025-04-08)
223 reads
There is a SET command in SQL Server that changes how much data is returned from some fields. This short post shows what I learned about the SET TEXTSIZE...
2025-04-25 (first published: 2025-04-07)
483 reads
By Chris Yates
The New Arena of Leadership The role of the Chief Data Officer is no...
Presenting you with an updated version of our sp_snapshot procedure, allowing you to easily...
SELECT * feels convenient, but in SQL Server it bloats I/O, burns network bandwidth,...
I've noticed several instances of what looks like a recursive insert with the format:...
Comments posted to this topic are about the item Cleaning Up the Cloud
Comments posted to this topic are about the item The Maximum Value in the...
I have a table with this data:
TravelLogID CityID StartDate EndDate 1 1 2025-01-01 2025-01-06 2 2 2025-01-01 2025-01-06 3 3 2025-01-01 2025-01-06 4 4 2025-01-01 2025-01-06 5 5 2025-01-01 2025-01-06I run this code:
SELECT IDENT_CURRENT('TravelLog')I get the value 5 back. Now I do this:
SET IDENTITY_INSERT dbo.TravelLog ON INSERT dbo.TravelLog ( TravelLogID, CityID, StartDate, EndDate ) VALUES (25, 5, '2025-09-12', '2025-09-17') SET IDENTITY_INSERT dbo.TravelLog OFFI now run this code.
DBCC CHECKIDENT(TravelLog) GO INSERT dbo.TravelLog ( CityID, StartDate, EndDate ) VALUES (4, '2025-10-14', '2025-10-17') GOWhat is the value for TravelLogID for the row I inserted for CityID 4 and dates starting on 14 Oct 2025? See possible answers