SQLBIGeek’s Function Friday – Convert Job Duration to Seconds
Welcome to the second post of my “SQLBIGeek’s Function Friday” blog series. In this series, I am...
Welcome to the second post of my “SQLBIGeek’s Function Friday” blog series. In this series, I am...
Today we have a guest editorial from Rodney Landrum that talks about life in the past, when we couldn't look up everything on the Internet.
Learn to use recursion to determine which row caused your merge statement to fail in this article.
As your database grows in size, Analysis Services cubes that use that database grow along with it. As such, one...
Conditional Split is one of the most commonly used transforms in any SSIS Package development routine. The limitation with conditional split is that any record that satisfies the first condition from the conditions list is routed to its corresponding path exclusively. In a logical sense, a record might satisfy more than one condition and one might want the record to be routed to all paths for processing, but with the Conditional Split transform this is not possible. We need a more intelligent conditional split where we can selectively route the records to more than one output path. In this tip we will look at how to facilitate this intelligent conditional split.
This article shows us a different way of finding all records between 2 dates.
You believe that an index is unused and so could be removed, and yet, your finger hovers nervously over the metaphorical "delete" button. You can't quite bring yourself to do it. Is it really safe to drop this index? Tony wonders if "invisible indexes" might solve this dilemma.
Steve Jones has a day off before SQL Server Connections and brings us a blooper reel for Halloween.
This challenge involves writing a logic to change the column position of values in the output based on the presence and absence of other values on each output row.
It’s actually kind of cool that SQL Rally voting for the pre-conference seminars and voting in the real(ish) world in the USA are coinciding. I’m in the running for the pre-con AND I’m volunteering for an actual election campaign for the first time ever.
By Brian Kelley
I will be leading an in-person Certified Information Systems Auditor (CISA) exam prep class...
EightKB is back again for 2026! The biggest online SQL Server internals conference is...
By HeyMo0sh
Working in DevOps long enough teaches you two universal truths: That’s exactly why I...
Hi all, I just started using VS Code to work with DB projects. I...
Comments posted to this topic are about the item Fun with JSON II
Comments posted to this topic are about the item Changing Data Types
I have some data in a table:
CREATE TABLE #test_data
(
id INT PRIMARY KEY,
name VARCHAR(100),
birth_date DATE
);
-- Step 2: Insert rows
INSERT INTO #test_data
VALUES
(1, 'Olivia', '2025-01-05'),
(2, 'Emma', '2025-03-02'),
(3, 'Liam', '2025-11-15'),
(4, 'Noah', '2025-12-22');
If I run this query, how many rows are returned?
SELECT t1.[key] AS row,
t2.*
FROM OPENJSON(
(
SELECT t.* FROM #test_data AS t FOR JSON PATH
)
) t1
CROSS APPLY OPENJSON(t1.value) t2; See possible answers