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

Advice I Like: Failure

By

If it fails where you thought it would fail that is not a failure....

Data Conferences – Worth Every Dollar

By

Some of the best career enhancers you can buy.   Why I Go to...

SQL Server 2025 RegEx and AI

By

One of the language changes in SQL Server 2025 that I’ve seen a lot...

Read the latest Blogs

Forums

A Place where AI Technology Shines

By Steve Jones - SSC Editor

Comments posted to this topic are about the item A Place where AI Technology...

Alternate for xp_delete_file

By PJ_SQL

alternate for xp_delete_file

Select @ for different fields

By bswhipp

I have a need where I need to pass a field name to a...

Visit the forum

Question of the Day

Getting the Object Code

What happens when I run this on SQL Server 2022 in the AdventureWorks2022 database?

SELECT OBJECT_DEFINITION (OBJECT_ID(N'dbo.uspGetBillofMaterials')) AS [Object Definition]; 
GO 

See possible answers