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.

SQLServerCentral Editorial

The Impact of Small Changes

A year ago, I started a monthly blogging event for the PostgreSQL community, inspired by T-SQL Tuesdays. I decided to call it PGSQL Phriday. (Time will tell if my insistence on trying to use a literation was a good idea or not.) Like the event for the SQL Server community, we ask someone to be […]

Blogs

The Book of Redgate: Spread across the world

By

This was Redgate in 2010, spread across the globe. First the EU/US Here’s Asia...

Merry Christmas

By

Today is Christmas and while I do not expect anybody to actual be reading...

Self-Hosting a Photo Server the Whole Family Can Use

By

Until recently, my family's 90,000+ photos have been hidden away in the depths of...

Read the latest Blogs

Forums

Happy Holidays, Let's Do Nerdy Stuff

By Grant Fritchey

Comments posted to this topic are about the item Happy Holidays, Let's Do Nerdy...

UNISTR Escape

By Steve Jones - SSC Editor

Comments posted to this topic are about the item UNISTR Escape

Celebrating Tomorrow

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Celebrating Tomorrow

Visit the forum

Question of the Day

UNISTR Escape

In SQL Server 2025, I run this command:

SELECT UNISTR('*3041*308A*304C\3068 and good night', '*') as "A Classic";
What is returned? (assume the database has an appropriate collation) A: B: C:

See possible answers