Menu
Are there any industry standard naming conventions for naming schemas in SQL Server?
Unfortunately a few reserved words such as admin describe my planned schemas the most clearly. To get around this I have been debating on making the schema names plural, but in a way that doesn't make sense, and will cause an issue with the Products.Products schema and table.
So I was wondering if there was any clear convention that Microsoft or the industry uses?
915
Use Simple, Descriptive Column Names Avoid short and cryptic names like pkg_fk; others won't know what that means. Descriptive names make it easier for others to understand the schema, which is vital to maintaining efficiency as the team grows. Don't use ambiguous names for polymorphic data.
Though these vary somewhat between SQL “flavors”, SQL columns and table names should begin with a letter, not end in an underscore, and should contain only alphanumeric characters. Column and table names should not contain spaces.
A Schema in SQL is a collection of database objects associated with a database. The username of a database is called a Schema owner (owner of logically grouped structures of data). Schema always belong to a single database whereas a database can have single or multiple schemas.
The dbo schema is the default schema of every database. By default, users created with the CREATE USER Transact-SQL command have dbo as their default schema. The dbo schema is owned by the dbo user account.
I found this reference for SQL Server Name Conventions
SQL Server Name Convention and T-SQL Programming Style
It says to use lowercase and no plurals in schemas
101
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
