Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion SQL Server Name Convention and T-SQL Programming Style.md
Original file line number Diff line number Diff line change
Expand Up @@ -325,7 +325,7 @@ SQL Server T-SQL Coding Conventions, Best Practices, and Programming Guidelines.
4. All [Service Broker statements](https://docs.microsoft.com/sql/t-sql/statements/send-transact-sql):
> If the SEND statement isn't the first statement in a batch or stored procedure, the preceding statement must be terminated with a semicolon (;).

- All script files should end with `GO` and line break. This is neccesary for batching scripts run throw `sqlcmd` or another tools.
- All script files should end with `GO` and line break. This is necessary for batching scripts run through `sqlcmd` or another tools.
- Keywords should be in **UPPERCASE**: `SELECT`, `FROM`, `GROUP BY` etc. This increases the readability of the code.
- Data types declaration should be in **lowercase**: `varchar(30)`, `int`, `real`, `nvarchar(max)` etc.
More details [here](https://www.sentryone.com/blog/aaronbertrand/backtobasics-lower-case-data-types).
Expand Down