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 […]
2019-12-10
23,240 reads
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
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.
2008-02-29 (first published: 2007-03-07)
14,860 reads
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.
2005-10-03
25,191 reads
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.
2008-06-20 (first published: 2005-04-06)
52,113 reads
New columnist Gregory Larsen used to not care what his objects were called until recently when he began to become concerned with the system generated constraint names. This short article tells you why.
2002-08-16
7,133 reads
A look at coding standards in SQL Server. The first part of this series deals with object naming standards.
2007-10-02 (first published: 2002-05-09)
49,193 reads
In this article by Mattias Fagerlund, he shows you how he employs strict database naming standards and conventions to make his job easier.
2001-12-13
11,242 reads
Learn the key basics of writing quality Transact-SQL code.
2001-09-07
6,666 reads
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.
2007-09-22 (first published: 2001-05-29)
28,114 reads
By Steve Jones
I love Chicago. I went to visit three times in 2023: a Redgate event,...
By Brian Kelley
I have found that non-functional requirements (NFRs) can be hard to define for a...
You can find the slidedeck for my Techorama session “Microsoft Fabric for Dummies” on...
Testing with AG on Linux with Cluster=NONE. it was all going ok and as...
Hi, I have two tables: one for headers with 9 fields and another for...
We're trying to understand how quick new versions of SQL server can be. Obviously...
Let’s consider the following script that can be executed without any error on both SQL Sever and PostgreSQL. We define the table t1 in which we insert three records:
create table t1 (id int primary key, city varchar(50)); insert into t1 values (1, 'Rome'), (2, 'New York'), (3, NULL);If we execute the following query, how will the records be sorted in both environments?
select city from t1 order by city;See possible answers