External Article

Formatting SQL Code - Part the Second

When you're formatting SQL Code, your objective is to make the code as easy to read with understanding as is possible, in a way that errors stand out. The extra time it takes to write code in an accessible way is far less than the time saved by the poor soul in the future, possibly yourself, when maintaining or enhancing the code. There isn't a single 'best practice, but the general principles, such as being consistent, are well-established. Joe Celko gives his take on a controversial topic.

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

PostgreSQL String Functions Part 1

By Shivayan Mukherjee

Comments posted to this topic are about the item PostgreSQL String Functions Part 1

Working Better Under Pressure

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Working Better Under Pressure

Identities and Sequences V

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Identities and Sequences V

Visit the forum

Question of the Day

Identities and Sequences V

When thinking about the identity property and sequence objects, which of these can generate values before an insert statement is executed?

See possible answers