2019-03-15
797 reads
2019-03-15
797 reads
When you are setting up a new SQL Server machine you need to determine how big you should make tempdb. To make sure you size tempdb appropriately you should monitor the tempdb space usage. If there are autogrowth events occurring after you have recycled SQL Server than you might want to increase the size of your tempdb data files. If tempdb never uses most of the tempdb space, then you might want to consider decreasing the size of tempdb.
2018-08-21
4,154 reads
Have you ever checked the size of the SQL Server tempdb after restarting SQL Server to find that it's reset? Simon Liew explains this behaviour.
2017-05-31
3,326 reads
TEMPDB doesn't have to be a black box. Know what objects and processes are causing it to bloat in size.
2017-01-30 (first published: 2016-12-29)
2,232 reads
2016-10-07 (first published: 2016-09-20)
1,554 reads
2016-08-29
1,224 reads
2016-07-28
1,191 reads
2016-07-06
1,307 reads
2016-05-03
1,510 reads
2016-04-26
1,261 reads
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