Articles

External Article

BIT of a Problem

The BIT data type is an awkward fit for a SQL database. It doesn't have just two values, and it can do unexpected things in expressions. What is worse, it is a flag rather than a predicate, and so its overuse, along with bit masks, is a prime candidate for being listed as a 'SQL Code Smell'. Joe Celko makes the case.

2011-01-24

3,676 reads

External Article

LINQ Lycanthropy: Transformations into LINQ

LINQ is one of the few technologies that you can start to use without a lot of preliminary learning. Also, it lends itself to learning by trying out examples. With Michael Sorens' help, you can watch as your conventional C# code changes to ravenous LINQ before your very eyes.

2011-01-21

3,948 reads

Blogs

Fabric Mirroring doesn’t start copying Rows

By

A short blog post about an issue with Fabric Mirroring (with Azure SQL DB...

JSON_OBJECTAGG is an Aggregate: #SQLNewBlogger

By

I wrote an article recently on the JSON_OBJECTAGG function, but neglected to include an...

Cultural Change: Fostering a Cost-Aware Culture in Your Organisation

By

After working deep in cloud operations, I’ve learned that FinOps isn’t really about dashboards...

Read the latest Blogs

Forums

Creating a JSON Document I

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Creating a JSON Document I

Who is Irresponsible?

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Who is Irresponsible?

Designing Database Changes Before Deployment: Level 1 of the Stairway to Reliable Database Deployments

By Massimo Preitano

Comments posted to this topic are about the item Designing Database Changes Before Deployment:...

Visit the forum

Question of the Day

Creating a JSON Document I

I want to create a JSON document that contains data from this table:

TeamID  TeamName  City          YearEstablished
1       Cowboys   Dallas        1960
2       Eagles  Philadelphia  1933
If I run this code, what is returned?
SELECT json_objectagg('Team' : TeamName)
FROM dbo.NFLTeams;

See possible answers