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

Future-Proofing: How to Stay Ahead in FinOps

By

Cloud environments don’t sit still. Pricing models change, services evolve, workloads grow, and suddenly...

Introducing the SQL Server on Kubernetes Operator

By

Are you considering replatforming your SQL Server workload due to recent vendor changes, but...

Advice I Like: Rewards from Work

By

The greatest rewards come from working on something that nobody has words for. If...

Read the latest Blogs

Forums

Removing TDE

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Removing TDE

Poor Names

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Poor Names

The day-to-day pressures of a DBA team, and how we can work smarter with automation and AI

By Terry Jago

Comments posted to this topic are about the item The day-to-day pressures of a...

Visit the forum

Question of the Day

Removing TDE

How do I remove TDE encryption of data from database xxx?

See possible answers