cancel
Showing results for 
Search instead for 
Did you mean: 
Data Engineering
Join discussions on data engineering best practices, architectures, and optimization strategies within the Databricks Community. Exchange insights and solutions with fellow data engineers.
cancel
Showing results for 
Search instead for 
Did you mean: 

notebooks naming convention

ElaPG
New Contributor III

I have read info about objects names but are there any best practices regarding notebooks naming convention?

1 REPLY 1

Rajeev45
Databricks Employee
Databricks Employee

It is recommended to name notebooks descriptively so that it is easy to understand their purpose and content. A good practice is to follow a consistent naming convention to help keep notebooks organized. These are some of general practices

  1. Use naming conventions that describe the notebook's function and contents. This can include the project name, dataset used, task name or category.
  2. Use dashes (-) or underscores (_) instead of spaces when separating words in the notebook name.
  3. Begin each notebook name with a prefix representing the notebook type or project name to easily identify related notebooks.
  4. Keep notebook names concise and limit them to 30 characters or less to ensure the name is fully visible in the Databricks workspace.
  5. Avoid special characters or symbols in notebook names.

Join Us as a Local Community Builder!

Passionate about hosting events and connecting people? Help us grow a vibrant local community—sign up today to get started!

Sign Up Now