Articles

External Article

What If You Really DO Need to Shrink a Database?

You’ve heard that shrinking a database is bad because it introduces both external and internal fragmentation, it causes blocking, it causes transaction log growth while it runs, and it’s slow and single-threaded. You understand that if it’s just a matter of 10-20-30% of a database, and the database is only 100-200GB, you might as well just leave the space there, because you’re gonna end up using it anyway.

2020-07-29

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

Breaking SQL Server for disaster recovery practice

By chapwolff

Hey all. I understand if this gets taken down due to the subject matter...

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?

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