External Article

Developing Modifications that Survive Concurrency

You can create a database under the assumption that SQL looks after all the problems of concurrency. It will probably work fine under test conditions: then, in the production environment, it starts losing data in subtle ways that defy repetition. It is every Database Developer's nightmare. In an excerpt from his acclaimed book, Alex Kuznetsov explains why it happens, and how you can avoid such problems.

Blogs

Data Engineering Books Worth Having on Your Shelf (or your tablet)

By

Good documentation gets you started. Good books get you deep. After years of working...

SSMS Evaluation – future ready

By

In previous posts, we looked at the SQL Server engine. for us DBAs, the...

Claude.ai vs Claude API

By

You have used Claude. But which Claude? The Claude app (claude.ai, the desktop and...

Read the latest Blogs

Forums

SQL Server Showing Out of Space But Plenty of Drive Space

By AMCity

We have a SQL Server installed. We have a 500GB drive for the database....

Creating a JSON Document IV

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Creating a JSON Document IV

Visit the forum

Question of the Day

Creating a JSON Document IV

I have this data in a table called dbo.NFLTeams

TeamID  TeamName       City             YearEstablished
------  --------       ----             ---------------
1       Cowboys        Dallas           1960
2       Eagles         Philadelphia     1933
3       Packers        Green Bay        1919
4       Chiefs         Kansas City      1960
5       49ers          San Francisco    1946
6       Broncos        Denver           1960
7       Seahawks       Seattle          1976
8       Patriots       New England      1960
If I run this code, how many rows are returned?
SELECT 
  YearEstablished,
  json_objectagg(city : TeamName)
FROM dbo.NFLTeams
GROUP BY  YearEstablished;

See possible answers