Formatting Database Names in Technical Documentation
Formatting Database Names in Technical Documentation records the relevant Microsoft Style Guide convention while keeping it explicitly house-style scoped rather than presenting it as a universal grammar rule.
ReviewedEvidence3 sourcesSectionWriting & Style
Quick answer
Use bold for database names in prose; use code style when the database name appears in code syntax.
Key details
Core IssueMicrosoft distinguishes ordinary prose references from code-syntax presentations of database names.
RegisterMicrosoft technical and professional documentation
Important caveats
Scope Boundary
The capitalization of an actual database name varies, so reproduce the documented name rather than normalizing its case.
Further guidance
Content
Use bold for database names in prose; use code style when the database name appears in code syntax.
Purpose
Microsoft distinguishes ordinary prose references from code-syntax presentations of database names.
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.
Formatting Event Names in Technical Documentation records a distinct Microsoft Style Guide authoring convention and keeps it explicitly scoped to technical documentation rather than presenting it as a universal grammar rule.
Formatting File Names in Technical Documentation records the relevant Microsoft Style Guide convention while keeping it explicitly house-style scoped rather than presenting it as a universal grammar rule.
Capitalizing Product Names in Technical Documentation records the relevant Microsoft Style Guide convention while keeping it explicitly house-style scoped rather than presenting it as a universal grammar rule.
Formatting AI Prompts in Technical Documentation records a distinct Microsoft Style Guide authoring convention and keeps it explicitly scoped to technical documentation rather than presenting it as a universal grammar rule.
Formatting Attributes in Technical Documentation records a distinct Microsoft Style Guide authoring convention and keeps it explicitly scoped to technical documentation rather than presenting it as a universal grammar rule.
Formatting Classes in Technical Documentation records a distinct Microsoft Style Guide authoring convention and keeps it explicitly scoped to technical documentation rather than presenting it as a universal grammar rule.
Formatting Code Keywords in Technical Documentation records a distinct Microsoft Style Guide authoring convention and keeps it explicitly scoped to technical documentation rather than presenting it as a universal grammar rule.
Formatting Code Samples in Technical Documentation records a distinct Microsoft Style Guide authoring convention and keeps it scoped to technical instructions rather than presenting it as a universal grammar rule.
