How to structure your BigQuery resources

[@MarkCollins-x7c]

Using standardised terminology would seem more intuitive. 2:22 - why call a database a project? For the uninitiated it can get very confusing when terms are ambiguous or mean different things depending on the context.

[@Piliponful]

I didn't understand a word

[@MichaelDouglas-ke4th]

From a business perspective, how should datasets be logically organized? Is it a bad idea to break up datasets by client (1 dataset for each client)? Or should datasets be organized by business department (marketing, finance, etc)? Any resources/directions/best practices here would be appreciated! Thanks!

[@leighajarett221]

Hi Michael! It really depends on your data needs - either one can work! I would consider both the access that your users need on your data, and what types of questions they are asking on the data. For example, if you are usually querying across multiple customers, having that information segmented across multiple datasets might be more difficult to manage them having it in a central location. But, if there are groups of users that should only have access to certain customer data, then it might make more sense to keep each customer in its own dataset

[@dheer211]

Very useful tips thank you

[@samk_jg]

Amazing tutorial !!

[@EllamSivam]

Useful information

[@ibrahimguzelbaba6994]

On 5:15, Common Storage Project and Compute Projects are mentioned. Are they named differently because of their intended use, or are there any differences in creation?