External Article

One use case for NOT using schema prefixes

I’ve long been a huge advocate for always referencing objects with a schema prefix in SQL Server.

In spite of what may be a controversial title to many of my regular blog readers, I don’t really want you to stop that practice in most of your T-SQL code, because the schema prefix is important and useful most of the time. At Stack Overflow, though, there is a very specific pattern we use where not specifying the schema is beneficial.

Blogs

The Intersection Between DevOps and FinOps

By

DevOps is about shortening the system development lifecycle. Plan faster, build faster, test faster,...

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...

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