Articles

External Article

Finding a better candidate for your clustered indexes

When creating tables it is difficult to determine exactly how the data will be accessed. Therefore when clustered indexes are chosen they are often just the ID column that makes the row unique. This may be a good choice, but once the application has been used and data access statistics are available you may need to go back and make some adjustments to your tables to ensure your clustered indexes are providing a benefit and not a drain on your applications.

2008-12-26

3,880 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

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