Formatting Database Table and Column Names

Key details

Core Issueformatting database table and column names

RegisterMicrosoft Learn technical documentation

Important caveats

Scope Boundary

This convention applies to table and column identifiers as code-like elements; ordinary prose references to a database as a product or service may follow different conventions.

Further guidance

Content

Use code style for database table and column names in Microsoft Learn technical content.

Purpose

Keep programmatic or structural text visually consistent and easier for readers to interpret in Microsoft Learn documentation.

Sources and evidence

Sources are shown with the role they play in this guide. Historical or style-sensitive claims are kept within the evidence boundary described above.

Text formatting guidelines — Microsoft Learn Contributor Guide (opens in a new tab)Microsoft · Current Microsoft Learn contributor guidance for Git repository/branch names, code style, package and database names, nonlocalized resource names, fenced code blocks, language tags, headings, and link text.

Related guides

Writing & Style

Formatting Git Repository and Branch Names

Formatting Git Repository and Branch Names records a distinct Microsoft Learn authoring convention and keeps it scoped to that documentation environment rather than presenting it as a universal grammar rule.

Writing & Style

Formatting Nonlocalized Resource Names

Formatting Nonlocalized Resource Names records a distinct Microsoft Learn authoring convention and keeps it scoped to that documentation environment rather than presenting it as a universal grammar rule.

Writing & Style

Formatting NuGet Package Names

Formatting NuGet Package Names records a distinct Microsoft Learn authoring convention and keeps it scoped to that documentation environment rather than presenting it as a universal grammar rule.

Explore the topic

Style Guides Technical Documentation Microsoft Learn Documentation