Additional Articles


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.

2023-09-13

External Article

Working around schema drift in SQL Server

At Stack Overflow, our environment has multiple implementations of a largely – but not 100% – identical schema. (By “schema,” I mostly mean the set of tables within a database.) I sometimes need to retrieve or update data across a large number of sites. Let’s say, pulling or removing information from the Users table, and related tables, across all of our databases.

2023-09-01

Blogs

Where Is My SQL Agent? Running Scheduled Jobs Against Azure SQL Database

By

One of the first things I review when I inherit a new SQL Server...

AgentDBA vs Critical SQL Server

By

It’s 07:43. Someone’s already left a message. “Something’s wrong with the DB server.” You...

Finally Cleaning Up Dropbox: Moving Almost a TB to Google Drive with rclone

By

I’ve had a Dropbox account for years. Like a lot of people, I started...

Read the latest Blogs

Forums

Follow Your Hunch

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Follow Your Hunch

What Happens When You Ask a Local AI to Query Your Database?

By Kumar Abhishek

Comments posted to this topic are about the item What Happens When You Ask...

Detecting Characters

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Detecting Characters

Visit the forum

Question of the Day

Detecting Characters

I have a SQL Server 2022 English default installation on a server. I want to detect if there are any upper case characters in rows and I have this code:

SELECT CustomerNameID,
       CustomerName
 FROM dbo.CustomerName
 WHERE CustomerName = LOWER(CustomerName)
Here is the sample data I am testing with:
CustomerNameID CustomerName
1              John Smith
2              Sarah Johnson
3              MICHAEL WILLIAMS
4              JENNIFER BROWN
5              david jones
6              emily davis
7              Robert Miller
8              LISA WILSON
9              christopher moore
10             Amanda Taylor
How many rows are returned?

See possible answers