Last week Andy launched a new series about Worst Practices by talking about why the Hungarian naming convention is bad for column names. This week he's at it again, declaring that the practice of having objects owned by anyone other than dbo is BAD! Agree or disagree, we think you'll enjoy reading this article and adding your thoughts to the discussion!
2019-08-01 (first published: 2002-09-12)
38,423 reads
The second part of Steve Jones' series on coding standards within SQL Server.
2011-03-04 (first published: 2002-07-01)
31,205 reads
Brief introduction to Apache v2.0 with links to performance/setup and installation and other information.
2002-05-03
692 reads
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,...
Quite the title, so let me set the stage first. You have an Azure...
Comments posted to this topic are about the item Rollback vs. Roll Forward
Comments posted to this topic are about the item Foreign Keys - Foes or...
Comments posted to this topic are about the item Fun with JSON I
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