I thought my database was collation agnostic
My struggles with a customer's database that used a different collation sequence. The easy way is never the right way, or is it?
2018-06-08 (first published: 2016-01-14)
4,554 reads
Thomas Romeo
- Interests: Love being a dad and husband. Love to cook. Love to taste.
GUIDs GUIDs everywhere, but how is my data unique?
After having seen many systems that use GUIDs as the primary key for every table, it is time to say enough is enough.
2014-12-18
9,969 reads
Blogs
Rolling Back a Broken Release
By Steve Jones
We had an interesting discussion about deployments in databases and how you go forward...
A bespoke reporting solution doesn’t have to cost the earth
By ChrisJenkins
You could be tolerating limited reporting because there isn’t an off the shelf solution...
Presenting with Visual Studio Code
A while back I wrote a quick post on setting up key mappings in...
Forums
Remotely Engineer Fabric Lakehouse objects: The Fabric Modern Data Platform
Comments posted to this topic are about the item Remotely Engineer Fabric Lakehouse objects:...
Creating JSON III
Comments posted to this topic are about the item Creating JSON III
Testing is Becoming More Important
Comments posted to this topic are about the item Testing is Becoming More Important
Question of the Day
Creating JSON III
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