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

Getting the SQL Server MCP Server Running

By

If you’ve wanted a SQL Server MCP server for your databases, it’s available. The...

Introducing azsql-migration-test: Test and Validate Azure SQL Database Migrations

By

Introducing azsql-migration-test, a small open-source CLI that validates your Azure SQL Database migrations against...

Rambling about Data on Wheels – origins, branding, expansion

By

I have been asked many times about how the name “Data on Wheels” came...

Read the latest Blogs

Forums

Make It Routine

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Make It Routine

DBCC CHECKDB Limits III

By Steve Jones - SSC Editor

Comments posted to this topic are about the item DBCC CHECKDB Limits III

CROSS APPLY Fundamentals: Part 1

By Imran2629

Comments posted to this topic are about the item CROSS APPLY Fundamentals: Part 1

Visit the forum

Question of the Day

DBCC CHECKDB Limits III

On SQL Server 2025, does DBCC CHECKDB support Memory-Optimized tables?

See possible answers