Skip to content

Commit 23b94a6

Browse files
Update naming_conventions.md
1 parent 1337043 commit 23b94a6

1 file changed

Lines changed: 9 additions & 1 deletion

File tree

docs/naming_conventions.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ This document outlines the naming conventions used for schemas, tables, views, c
1212
3. [Column Naming Conventions](#column-naming-conventions)
1313
- [Surrogate Keys](#surrogate-keys)
1414
- [Technical Columns](#technical-columns)
15-
15+
4. [Stored Procedure](#stored-procedure-naming-conventions)
1616
---
1717

1818
## **General Principles**
@@ -69,3 +69,11 @@ This document outlines the naming conventions used for schemas, tables, views, c
6969
- `dwh`: Prefix exclusively for system-generated metadata.
7070
- `<column_name>`: Descriptive name indicating the column's purpose.
7171
- Example: `dwh_load_date` → System-generated column used to store the date when the record was loaded.
72+
73+
## **Stored Procedure Naming Conventions**
74+
75+
- All stored procedures used for loading data must follow the naming pattern: **`load_<layer>`**.
76+
- `<layer>`: Represents the layer being loaded, such as `bronze`, `silver`, or `gold`.
77+
- Example:
78+
- `load_bronze` → Stored procedure for loading data into the Bronze layer.
79+
- `load_silver` → Stored procedure for loading data into the Silver layer.

0 commit comments

Comments
 (0)