2015-05-01
1,798 reads
2015-05-01
1,798 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,263 reads
2014-03-27
2,362 reads
2013-06-05
2,452 reads
2013-05-10
2,260 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,553 reads
2010-06-17
3,956 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 Steve Jones
I’m not sure I knew identity column values could not be updated. I ran...
By Steve Jones
We had an interesting discussion about deployments in databases and how you go forward...
By ChrisJenkins
You could be tolerating limited reporting because there isn’t an off the shelf solution...
I have mentioned this several times over several years. Can someone please help me...
SELECT COUNT(DISTINCT Component) AS Found FROM tblComponents WHERE(Component NOT LIKE '%[a-z]%') AND(LTRIM(RTRIM(Component)) = 'GM13622')...
Comments posted to this topic are about the item Remotely Engineer Fabric Lakehouse objects:...
In a SQL Server 2025 table, called Beer, I have this data:
BeerIDBeerName 1Becks 2Fat Tire 3Mac n Jacks 4Alaskan Amber 8KirinI run this code:
SELECT JSON_OBJECTAGG(
BeerID: BeerName )
FROM beer;
What are the results? See possible answers