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

Simple Talks Episode 7

By

The season 1, seventh episode of Simple Talks is out. Check it out, with...

A New Word: the McFly effect

By

the McFly Effect – n. the phenomenon of observing your parents interact with people...

Key mappings in Visual Studio Code

By

At a recent conference I was asked how I executed code during my presentation....

Read the latest Blogs

Forums

Unstuck

By Ryan Booz

Comments posted to this topic are about the item Unstuck

Check sequential order of status of items

By SQL Bee

There is a table tblItems with below structure ( i cannot change the below...

Calling Invoke-Sqlcmd from powershell and passing an object containing a '-'

By axm1955@yahoo.com

Invoke-Sqlcmd -Query "ALTER AVAILABILITY GROUP $AAG REMOVE DATABASE $DB " -ServerInstance $Instance Invoke-Sqlcmd :...

Visit the forum

Question of the Day

Enable a Disabled Index

I have disabled the LoggerCI index on the dbo.Logger table. How do I enable it?

See possible answers