From 9072c1c919a7154a49cc999cd91b2d4e3f5333df Mon Sep 17 00:00:00 2001 From: Kevin Martin Date: Tue, 7 Feb 2023 16:02:47 -0600 Subject: [PATCH] Added text to reserved keywords. --- docs/findings/NamingConventions.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/findings/NamingConventions.md b/docs/findings/NamingConventions.md index fb71725..0a248c1 100644 --- a/docs/findings/NamingConventions.md +++ b/docs/findings/NamingConventions.md @@ -338,7 +338,9 @@ For all parts of the table name, including prefixes, use Pascal Case. `PascalCas ## Using Reserved Words in Name **Check Id:** 4 -Using reserved or future reserved words makes code more difficult to read, can cause problems to code formatters, and can cause errors when writing code. +Using reserved or future reserved words makes code more difficult to read, can cause problems to code formatters, and can cause errors when writing code. + +Sometimes SSMS will color code a word making you think it is a reserved keyword. It might just be a "special" word that is used in a database backup function somewhere. Check the Reserved Keyword link below. If the highlighted word in SSMS is not on the current or future reserved list, you are safe to use it as an object name. - See [Reserved Keywords](https://docs.microsoft.com/en-us/sql/t-sql/language-elements/reserved-keywords-transact-sql)