What’s In A Name?

Kevin Feasel

2017-03-21

Naming

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

One Part Name
vIndividualCustomer
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

Naming Procedures

Aaron Bretrand shares rules that he uses when naming stored procedures: I’ve talked about this in my live sessions, but this is an extreme case that really happened – a team took over a week to fix a bug in a stored procedure, and the delay was caused solely by poor naming standards. What happened […]

Read More

Field And Record

Kevin Feasel

2016-04-21

Naming

Michael Swart introduces Field & Record magazine: I’m definitely a descriptivist. Language is always changing and if a word or phrase gets adopted widely enough, it is no longer “wrong” (whatever that means). So when I hear “Field” and “Record” they’re acceptable to me. But if I’m explaining something, I don’t want to distract from […]

Read More

Categories

March 2017
MTWTFSS
« Feb Apr »
 12345
6789101112
13141516171819
20212223242526
2728293031