When naming a SQL Server instance, it is worth keeping a few practical rules in mind.
General rules
- Instance names are limited to 16 characters.
- The first character must be a letter.
- Names cannot contain spaces or special characters such as
\,/,:,*,?,",<,>, or|. - Avoid names that are difficult to distinguish from the host name or from other instances already in use.
- Keep names short, clear, and meaningful.
Good practice
In addition to the technical limits, a sensible naming convention will save confusion later.
A good instance name should:
- make it obvious what the instance is for
- be consistent across environments
- be easy for administrators and support teams to recognise
- avoid unnecessary abbreviations unless they are well understood internally
For example, you might choose names based on:
- application or service
- environment, such as
DEV,TEST, orPROD - region or business unit, if that is relevant
Examples
Reasonable examples might include:
APP01FINANCEREPORTINGCRMTEST
Poor examples might include:
SQL Server123SQLINSTANCE!THISISFARTOOLONGFORSQL
Final thought
The technical rules are simple, but the operational impact of a poor naming convention can linger for years. A clear, consistent standard is usually worth agreeing early.