Skip to content

database-identifiers.md

Latest commit

 

History

History
153 lines (107 loc) · 8.87 KB

database-identifiers.md

File metadata and controls

153 lines (107 loc) · 8.87 KB
title Database Identifiers
description Get acquainted with database identifiers. Learn about their collation, various classes, delimiting requirements, and naming rules.
author WilliamDAssafMSFT
ms.author wiassaf
ms.reviewer randolphwest
ms.date 03/30/2026
ms.service sql
ms.subservice configuration
ms.topic concept-article
ms.custom
ignite-2025
helpviewer_keywords
regular identifiers [SQL Server]
identifiers [SQL Server]
names [SQL Server], identifiers
identifiers [SQL Server], about identifiers
SQL Server identifiers
Transact-SQL identifiers
database objects [SQL Server], names
dev_langs
TSQL
monikerRange >=aps-pdw-2016 || =azuresqldb-current || =azure-sqldw-latest || >=sql-server-2016 || >=sql-server-linux-2017 || =azuresqldb-mi-current || =fabric || =fabric-sqldb

Database identifiers

[!INCLUDE SQL Server Azure SQL Database Synapse Analytics PDW FabricSE FabricDW FabricSQLDB]

The database object name is referred to as its identifier.

Servers, databases, and database objects, such as tables, views, columns, indexes, triggers, procedures, constraints, and rules, can have identifiers. Most objects require identifiers, but some objects, such as constraints, make them optional.

You create an object identifier when you define the object. Use the identifier to reference the object. For example, the following statement creates a table with the identifier TableX, and two columns with the identifiers KeyCol and Description:

CREATE TABLE TableX (
    KeyCol INT PRIMARY KEY,
    Description NVARCHAR(80)
);

This table also has an unnamed constraint. The primary key constraint has no identifier, and so would be assigned a system-generated name like PK__TableX__D7CB9CCCEEF0806C, which you could observe in system metadata views like sys.key_constraints.

Constraint names and other schema-scoped objects must be unique within a database schema. For example, two primary key constraints can't share a name. However, column names only need to be unique within each table, not within the schema.

The collation of an identifier depends on the level at which you define it.

  • The default collation of the instance is assigned to identifiers of instance-level objects, such as logins and database names.
  • The default collation of the database is assigned to identifiers of objects in a database, such as tables, views, and column names. For example, you can create two tables with names that differ only in case in a database that has case-sensitive collation, but you can't create them in a database that has case-insensitive collation.

Note

The names of variables, or the parameters of functions and stored procedures must comply with the rules for [!INCLUDE tsql] identifiers.

Classes of identifiers

There are two classes of identifiers:

  • Regular identifiers comply with the rules for the format of identifiers. Regular identifiers aren't delimited when they're used in [!INCLUDE tsql] statements.

    USE AdventureWorks2022;
GO

SELECT *
FROM HumanResources.Employee
WHERE NationalIDNumber = 153479919;

  • Delimited identifiers are enclosed in double quotation marks (") or brackets ([ and ]). Identifiers that comply with the rules for the format of identifiers might not be delimited. For example:

    USE AdventureWorks2022;
GO

SELECT *
FROM [HumanResources].[Employee] --Delimiter is optional.
WHERE [NationalIDNumber] = 153479919 --Delimiter is optional.

Identifiers that don't comply with all the rules for identifiers must be delimited in a [!INCLUDE tsql] statement. For example:

USE AdventureWorks2022;
GO

--Identifier contains a space and uses a reserved keyword.
CREATE TABLE [SalesOrderDetail Table] (
    [Order] INT NOT NULL,
    [SalesOrderDetailID] INT IDENTITY(1, 1) NOT NULL,
    [OrderQty] SMALLINT NOT NULL,
    [ProductID] INT NOT NULL,
    [UnitPrice] MONEY NOT NULL,
    [UnitPriceDiscount] MONEY NOT NULL,
    [ModifiedDate] DATETIME NOT NULL,
    CONSTRAINT [PK_SalesOrderDetail_Order_SalesOrderDetailID] PRIMARY KEY CLUSTERED (
        [Order] ASC,
        [SalesOrderDetailID] ASC
    )
);
GO

SELECT *
FROM [SalesOrderDetail Table] --Identifier contains a space and uses a reserved keyword.
WHERE [Order] = 10; --Identifier is a reserved keyword.

Both regular and delimited identifiers must contain from 1 through 128 characters. For local temporary tables, the identifier can have a maximum of 116 characters.

Rules for regular identifiers

The names of variables, functions, and stored procedures must follow these rules for [!INCLUDE tsql] identifiers.

  1. The first character must be one of the following characters:

    • A letter as defined by the Unicode Standard 3.2. The Unicode definition of letters includes Latin characters from a through z, from A through Z, and also letter characters from other languages.

    • The underscore (_), at sign (@), or number sign (#).

      Certain symbols at the beginning of an identifier have special meaning in [!INCLUDE ssNoVersion]. A regular identifier that starts with the at sign always denotes a local variable or parameter and can't be used as the name of any other type of object. An identifier that starts with a number sign denotes a temporary table or procedure. An identifier that starts with double number signs (##) denotes a global temporary object. Although the number sign or double number sign characters can be used to begin the names of other types of objects, we don't recommend this practice.

      Some [!INCLUDE tsql] functions have names that start with double at signs (@@). To avoid confusion with these functions, don't use names that start with @@.

  2. Subsequent characters can include the following list:

    • Letters as defined in the Unicode Standard 3.2.

    • Decimal numbers from either Basic Latin or other national scripts.

    • The at sign (@), dollar sign ($), number sign (#), or underscore (_).

  3. The identifier must not be a [!INCLUDE tsql] reserved word. [!INCLUDE ssNoVersion] reserves both the uppercase and lowercase versions of reserved words. When you use identifiers in [!INCLUDE tsql] statements, delimit identifiers that don't comply with these rules by using double quotation marks or brackets. The words that are reserved depend on the database compatibility level. Set the database compatibility level by using the ALTER DATABASE compatibility level statement.

  4. Don't use embedded spaces or special characters.

  5. Don't use Supplementary characters.

When you use identifiers in [!INCLUDE tsql] statements, delimit identifiers that don't comply with these rules by using double quotation marks or brackets.

Some rules for the format of regular identifiers depend on the database compatibility level.

Catalog collation in Azure SQL Database

You can't change or set the logical server collation on Azure SQL Database. However, you can configure each database's collations separately for data in the database and for catalog. The catalog collation determines the collation for system metadata, such as object identifiers. You can specify both collations independently when you create the database in the Azure portal, in T-SQL with CREATE DATABASE, or in PowerShell with New-AzSqlDatabase.

For details and examples, see CREATE DATABASE. Specify a collation for the database (COLLATE) and a catalog collation for system metadata and object identifiers (CATALOG_COLLATION).

Catalog collation in SQL database in Microsoft Fabric

Currently, by default the collation of a SQL database in Fabric is SQL_Latin1_General_CP1_CI_AS, but this can be configured when deploying. The collation can't be updated after deployment. Collations on individual columns are supported. For more information on deployment options, see Options to create a SQL database in Fabric.

Related content