Would like to ask about using of schemas in Sql Server 2019. For now we are using numbers as schemas for procedures and functions:
2 etc. to version procedures and functions. For example
.[GetFirstName] is the newest version of procedure but we have also node where we has to use
.[GetFirstName] procedure (for example to compare efficiency between old and new).
For tables and views we are not using schemas but I am thinking about adding below:
- conf - Configuration - for table which store confiuration data
- dict - Dictionary - for table which store dictionaries
- log - Logging - for table which store logs
- proc - Processing - for tables which wille be use to massive updates and insert commands (~ 300 insert/updates per seconds)
- Do you think that using procedure version as schema is a good idea ?
Is it good idea to have different idea for schemas in tables/views (responsible of table) and in procedure/functions (versioning)
Do you think that using below schema preposition is a good idea ? What problems can I have in future in process of addministration/change on production ?
Do you have any idea (except schemas) how to name tables with config,dictionaries,processing ? Is it worth to divide them in groups by for example add substring at the end (StatusDict, EventDict, StatusConfig, EventConfig, TransactionProc) etc. ? I would add that I am using naming convenction from: SQL Server Name Convenction. Beacuse of naming tables like I describe above the ID for columns will be StatusDictID, EventDictID instead of StatusID, EventID.
Tank you in advance for answers.