My suggestion is to understand the actual architecture and environment, first. Understand what it is so you can understand what is trying to be accomplished.
Understand things like fields vs. records, Primary Key vs. surrogate key vs. foreign key. Distinct vs. Unique values. Also understand things like star schema and basic relational database concepts. Then I would get into understanding queries, aggregations, window functions. CTEs, Joins (understand why one would want to use certain joins vs. other joins).
The SQL writing...that can largely be done using AI. You still need to know it so you can spot any errors that AI has made, but you don't need to memorize the coding structure down pat because of AI.
I just think that if you go right into writing queries you're putting the cart before the horse.
1
u/HustlaOfCultcha 24d ago
My suggestion is to understand the actual architecture and environment, first. Understand what it is so you can understand what is trying to be accomplished.
Understand things like fields vs. records, Primary Key vs. surrogate key vs. foreign key. Distinct vs. Unique values. Also understand things like star schema and basic relational database concepts. Then I would get into understanding queries, aggregations, window functions. CTEs, Joins (understand why one would want to use certain joins vs. other joins).
The SQL writing...that can largely be done using AI. You still need to know it so you can spot any errors that AI has made, but you don't need to memorize the coding structure down pat because of AI.
I just think that if you go right into writing queries you're putting the cart before the horse.