Writing clear, logical, easy-to-read, and high-performance ETL pipelines in SQL is an important part of a data scientist’s day-to-day job. Recently, after reviewing multiple SQL style guides (see references), I reflected on my practices and identified the following 10 SQL best practices, more accurately, common mistakes I’ve made. I hope this can be helpful to you.
The benefits of following these SQL style best practices include:
- Improved code readability
- Reduced ambiguity
- Enhanced debugging efficiency
- Optimized code performance.
- Keywords and function names should all be lowercase.
Lower case are much easier for human to read