Data Documents and Common Sense
What can be so difficult in creating a sensible standard for Structured Data Documents? To understand why they tend to get improved into unusable complexity, I’ll need to explain a bit of background.
2025-01-06
What can be so difficult in creating a sensible standard for Structured Data Documents? To understand why they tend to get improved into unusable complexity, I’ll need to explain a bit of background.
2025-01-06
2025-01-08 (first published: 2025-01-03)
518 reads
2024-12-20
1,677 reads
Ever wonder all the reasons that we use databases instead of file systems? While we don’t think of it too much anymore, the first reason that databases came into existence was to remove redundancies.
2024-04-12
In this article, Joe Celko gives us a history of the different character sets that are used in computing and how that can pertain to your usage in relational databases. Some of these you may have never heard of!
2023-05-17
The VALUES clause makes inserting literal values into a table simple and easy. In this article, Joe Celko explains how to use the VALUES clause.
2022-07-01
Joe Celko explains how several mathematical concepts, combinations, permutations, and derangements, relate to databases.
2022-06-01
Everyone learns to calculate an average in school, but, as Joe Celko shows, there are better ways to summarize data.
2022-03-25
Joe Celko explains how missing data is handled from the printing press to databases.
2021-07-26
Database systems have powerful features built right in that can ensure the integrity of data. In this article, Joe Celko discusses keys and constraints.
2021-05-28
By HeyMo0sh
Working in DevOps, I’ve seen FinOps do amazing things for cloud cost control, but...
Every organization I talk to has the same problem dressed up in different clothes....
By DataOnWheels
I am delighted to host this month’s T-SQL Tuesday invitation. If you are new...
Comments posted to this topic are about the item The day-to-day pressures of a...
Hello all, I’m looking for advice on how to derive a daily snapshot table...
We need to replace our Windows server running SQL 2017. Any reason not to...
I have some data in a table that looks like this:
BeerID BeerName brewer beerdescription 1 Becks Interbrew Beck's is a German-style pilsner beer 2 Fat Tire New Belgium Toasty malt, gentle sweetness, flash of fresh hop bitterness. 3 Mac n Jacks Mac & Jack's Brewery This beer erupts with a floral, hoppy taste 4 Alaskan Amber Alaskan Brewing Alaskan Brewing Amber Ale is an "alt" style beer 8 Kirin Kirin Brewing Kirin Ichiban is a Lager-type beerIf I run this, what is returned?
select t1.[key]
from openjson((select t.* FROM Beer AS t for json path)) t1 See possible answers