Transcription of I. Naming Conventions
{{id}} {{{paragraph}}}
Example: marketing
I. Naming Conventions
SQL Server Standards Version Shane Lively & Michael Sarsany Page 1 of 24 I. Naming Conventions The main goal of adopting a Naming convention for database objects is so that you and others can easily identify the type and purpose of all objects contained in the database. The information presented here serves as a guide for you to follow when Naming your database objects. When reading these rules and guidelines, remember that consistent Naming can be the most important rule to follow. Please also keep in mind that following the guidelines as outlined in this document can still produce long and cryptic names, but will limit their numbers and impact. However, ultimately your unique situation will dictate the reasonability of your Naming convention.
Notation) - For all parts of the table name, including prefixes, use Pascal Case. Using this notation will distinguish your table names from SQL keywords (camelCase). For example, "select CustomerId, CustomerName from MyAppGroupTable where CustomerName = '%S'" shows the notation for the table name
Loading..
Tags:
Information
Domain:
Source:
Link to this page:
Please notify us if you found a problem with this document: