T-SQL Tuesday Retrospective #012: Why DBA skills are necessary
This is my ongoing series of answering T-SQL Tuesday posts far too late to be of any use. Click here if you want to read previous entries. Paul Randal...
2021-03-17
138 reads
This is my ongoing series of answering T-SQL Tuesday posts far too late to be of any use. Click here if you want to read previous entries. Paul Randal...
2021-03-17
138 reads
(If you would like to read the previous T-SQL Tuesday Retrospective entries, visit this link.) In October 2010, Sankar Reddy asked us which misconceptions we’ve been labouring under when...
2021-03-16 (first published: 2021-03-10)
310 reads
SQL Server is a complex beast, with many configuration options that can range from recommended to completely avoided. Since the release of SQL Server 2016, several options that were...
2021-03-03
62 reads
After the Professional Association of SQL Server (PASS) unceremoniously closed down in January this year and its video library & brand names were bought by Red Gate Software Ltd, it...
2021-02-24
100 reads
This Wednesday, from 5pm to 7pm Mountain Standard Time, the Calgary Data User Group is presenting two sessions for your virtual attendance. 15 minutes: A lightning talk on Kubernetes...
2021-02-22
23 reads
(Thanks to Erik Darling for reviewing this post. Check out his training materials.) One of the bigger clichés in the data professional vocabulary (behind “it depends”) is that you...
2021-04-20 (first published: 2021-02-17)
544 reads
Some years ago, I wrote about what it means to be “professional” (and that it doesn’t mean having to wear a suit and tie). Recently a conversation broke out...
2021-02-10
170 reads
(You can see previous T-SQL Tuesday retrospectives by visiting this link.) In September 2010, Michael J. Swart (blog | Twitter) invited us to talk about indexes. Indexes are strange...
2021-02-03
25 reads
(If you’d like to read my other T-SQL Tuesday Retrospective posts, click here.) In August 2010, Jason Brimhall (blog | Twitter) invited us to discuss preparing for vacations: “Write...
2021-01-27
14 reads
If you’re reading this, there’s a good chance you’re straight, white, male, and English-speaking. There’s also a high likelihood that you live in the United States. The technology industry...
2021-01-20
31 reads
By HeyMo0sh
Microsoft Fabric (not to be confused with the more general term “fabric” in DevOps)...
By James Serra
I’m honored to be hosting T-SQL Tuesday — edition #192. For those who may...
By Vinay Thakur
Continuing from Day 2 , we learned introduction on Generative AI and Agentic AI,...
Hi Team, I am trying to refresh the Azure Synapse Dedicated pool from production...
Looking for a creative and experienced mobile game development company that brings your game...
hi everyone I am not sure how to write the query that will produce...
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 *
FROM OPENJSON(
(
SELECT t.* FROM #test_data AS t FOR JSON PATH
)
) t; See possible answers