2015-05-01
1,799 reads
2015-05-01
1,799 reads
It sounds simple enough. Either your column will always have a value or it may not. Yet somehow such a seemingly simple decision can become a never-ending debate where database schema begins to resemble superstition and designing effective tables seems more contentious than you expected it to be.
2016-02-26 (first published: 2014-10-30)
27,316 reads
2014-03-27
2,363 reads
2013-06-05
2,453 reads
2013-05-10
2,263 reads
2012-05-11
3,357 reads
We all know NULL values must be dealt with carefully in T-SQL, but how exactly do you best deal with them in SQL XML?
2010-10-26
27,654 reads
2010-06-17
3,960 reads
2010-04-07
4,056 reads
The key to working with null values properly is to accommodate them consistently. Learn a few tricks that will help you do just that.
2009-09-16
4,497 reads
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) ...
By Brian Kelley
Professor Patrick Winston of MIT used to give a one-hour talk about how to...
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...
Comments posted to this topic are about the item Every Database Has Problems
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