What’s In A Name?

Kevin Feasel



Kenneth Fisher explains the different parts of an object name in SQL Server:

One Part Name
This is just the name of the object. This is probably the most common usage and yet the only one I would recommend never using. (I’ll freely admit I’m not great at this myself btw.) When you only use a single name the schema is implied by the default schema of the user running the statement. That means that the same statement run by two different users could have two different meanings. Since most users have a default schema of dbo this would probably hit the object dbo.vIndividualCustomer. Assuming one even existed.

Click through for more.

Related Posts

Generating Fake Company Names

Daniel Hutmacher has a great way of generating fake company names: This query is actually a lot simpler than it first appears. Here’s how it breaks down: Pick 100 words at random (table “a”) For each word in “a”, if possible, pick a single random word (“b”) that doesn’t start or end with the same […]

Read More

Names Matter

Chris Webb is concerned about the under-use of the name “Power Query”: In more recent times I’ve written posts with unwieldy names like “Introduction to Insert Topic Name Here in Power Query/Power BI/Excel 2016 Get & Transform” and in the future I suppose this will have to grow to “Introduction to Insert Topic Name Here in Power Query/Power BI/Excel […]

Read More


March 2017
« Feb Apr »