There are probably not many SQL Server DBAs that use the semicolon as a statement separator. In SQL Server 2005, this is required in certain places and new author Kenneth Powers brings us a look at where and why you need to use this syntax.
2007-10-02 (first published: 2006-01-09)
45,840 reads
By Steve Jones
I discovered a procedure recently that I wasn’t aware of: sp_sequence_get_range. This post looks...
By Arun Sirpal
After a year away getting to grips with AI and its application across the...
By SQLPals
Beware of Generic SQL Server License Keys (What to Use Instead) ...
i have huge table with lot of data and is also wide. i took...
Comments posted to this topic are about the item Creating a JSON Document II
By VishnuGupthanSQLPowershellDBA
Comments posted to this topic are about the item Backing Up Azure Key Vault...
I want to create a JSON document that contains data from this table:
TeamID TeamNameCity YearEstablished 1 Cowboys Dallas 1960 2 Eagles Philadelphia 1933 3 Packers Green Bay 1919 4 Chiefs Kansas City 1960If I run this code, what document(s) is/are returned?
SELECT json_objectagg( n.city : n.TeamName) FROM dbo.NFLTeams;See possible answers