From 750c2b48db5401870321bbe79d5472012ea2f9f9 Mon Sep 17 00:00:00 2001 From: samhaese <63563702+samhaese@users.noreply.github.com> Date: Fri, 26 Sep 2025 12:17:53 -0700 Subject: [PATCH 1/2] Typo: Change 'throw' to 'through' --- SQL Server Name Convention and T-SQL Programming Style.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/SQL Server Name Convention and T-SQL Programming Style.md b/SQL Server Name Convention and T-SQL Programming Style.md index 5f01ff49..7bbdc746 100644 --- a/SQL Server Name Convention and T-SQL Programming Style.md +++ b/SQL Server Name Convention and T-SQL Programming Style.md @@ -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 neccesary 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). From c3ec2201f4d12cf4b1a61c4659173c572cf8d582 Mon Sep 17 00:00:00 2001 From: samhaese <63563702+samhaese@users.noreply.github.com> Date: Fri, 26 Sep 2025 12:19:30 -0700 Subject: [PATCH 2/2] Typo: change neccesary to necessary --- SQL Server Name Convention and T-SQL Programming Style.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/SQL Server Name Convention and T-SQL Programming Style.md b/SQL Server Name Convention and T-SQL Programming Style.md index 7bbdc746..2e63ae48 100644 --- a/SQL Server Name Convention and T-SQL Programming Style.md +++ b/SQL Server Name Convention and T-SQL Programming Style.md @@ -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 through `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).