Naming Standards

SQLServerCentral Article

SQL Server Name Convention and T-SQL Programming Style

  • Article

There are only two hard things in Computer Science: cache invalidation and naming things -- Phil Karlton The recommendations in this article are not the ultimate truth. Please consider this article as a rule template that you can adapt to your needs. A naming convention is a set of rules for choosing the character sequence to […]

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(10)

You rated this post out of 5. Change rating

2019-12-10

25,487 reads

External Article

SQL Code Layout and Beautification

  • Article

William Brewer takes a look at the whole topic of SQL Code layout and beautification, an important aspect to SQL programming style. He concludes that once you are tired of laying SQL out by hand, you had better choose a tool with plenty of knobs to twiddle, because nobody seems to agree on the best way of doing it.

2008-05-26

6,244 reads

SQLServerCentral Article

Practical Methods: Naming Conventions

  • Article

Everyone should establish some sort of naming convention for their SQL Server platform. It helps to ensure that developers and DBAs can easily find objects and communicate with one another. New author Michael Lato brings us the start of a series on organizing your SQL Server code with an article on naming conventions.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(13)

You rated this post out of 5. Change rating

2008-02-29 (first published: )

15,192 reads

SQLServerCentral Article

Stored Procedure Naming Conventions

  • Article

As your SQL Server applications grow, chances are that you have more and more objects, especially stored procedures that you need to keep track of. An organized environment is key to being able to prevent the duplication of code and effort. Joe Sack brings us a look at how he names stored procedures to easy identification.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(7)

You rated this post out of 5. Change rating

2005-10-03

25,569 reads

SQLServerCentral Article

Best Practices for Database Design

  • Article

One of the few things that SQL Server does not automatically help you with is the design of your tales, views, and other database objects. Having standards and design techniques can greatly ease the maintenance of your schema as well as ease the transition to having others work with the database. New author J.D. Gonzalez brings us some of his naming techniques to keep things organized.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(115)

You rated this post out of 5. Change rating

2008-06-20 (first published: )

52,380 reads

SQLServerCentral Article

Database Standards and Conventions

  • Article

Having a good set of naming conventions for your SQL Server objects is one of the most vital things to a company. In the long duration of a business, it saves money and time as programmers are transferred internally and don't need to relearn object names. As learning curves lower, cost lowers. This article covers some of the conventions that Brian Knight uses and why he uses them.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(8)

You rated this post out of 5. Change rating

2005-02-25 (first published: )

28,398 reads

Blogs

How to Clear the SSMS Cache (SSMS 21 and Later)

By

How to Clear the SSMS Cache (SSMS 21 and Later) Updated...

The flight recorder: Replaying what an AI agent did on my SQL Server

By

“What exactly did it do on my server?” is the first question a DBA...

Announcements from the Microsoft Fabric Community Conference — Barcelona 2026

By

Microsoft shared a broad set of Fabric, Power BI, and SQL updates at FabCon...

Read the latest Blogs

Forums

Let's Talk Certifications

By Grant Fritchey

Comments posted to this topic are about the item Let's Talk Certifications

The Hidden Security Risks of Role Combination in SSAS Tabular

By Pablo Echeverria

Comments posted to this topic are about the item The Hidden Security Risks of...

The Empty Aggregate

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Empty Aggregate

Visit the forum

Question of the Day

The Empty Aggregate

I have this table in a SQL Server 2025 database:

CREATE TABLE [dbo].[CustomerOrder]
(
[OrderID] [int] NULL,
[CustomerID] [int] NULL,
[total] [money] NULL
) ON [PRIMARY]
GO
What is returned from this code? (answers are for the sum and then the count)
SELECT SUM(total) AS sum,
       COUNT(total) AS count
FROM dbo.CustomerOrder;



See possible answers