Power BI Journey: Blog #3

I am now in the third tutorial on Power BI. In this lesson, the topic is on creating and managing relationships. Important concepts that were introduced are cardinality i.e. many-to-1 (*-1) or (one-to-many (1-*), cross-filter where if we select "Both", this means that we can think of many separate tables as one table.

I have these three separate tables.

Apocalypse Sales:

Apocalypse Store:

Customer_Information:

Notice that each of the values in the Customer ID column of the third table can be seen in the Cust ID column of the first table. But notice that there are only four rows in Customer_Information table while there are many rows in the Apocalypse Sales table. The cardinality of the relationship means having unique or multiple instances per value for the joining field between two tables. This means that the cardinality of the relationship from Apocalypse Sales and Customer_information in terms of Customer ID = Cust ID is Many-to-one. Conversely, the cardinality of the relationship from Customer_information to Apocalypse Sales in terms of Customer ID = Cust ID is one-to-many. If we relate this to SQL, Customer ID is the Primary Key.

Using the same principle, the cardinality of the relationship between Apocalypse Store and Apocalypse Sales in terms of Product_ID is one-to-many. Conversely, the cardinality of the relationship between Apocalypse Sales and Apocalypse Store in terms of Product_ID is many-to-one.

This is the reason why we have the following model.

As an output, I was able to create a table that list the different states associated with each customer and then determine the number of product ids each customer purchased.

In other words, in the Apocalypse Store, we have 10 products being sold and the customer from Minnesota state has purchased 7 out of the 10 products.

Comments

Privacy Policy of ShinStats: descriptives calc

Privacy Policy Shin Nix built the ShinStats app as an Ad Supported app. This SERVICE is provided by Shin Nix at no cost and is intended for use as is. This page is used to inform visitors regarding my policies with the collection, use, and disclosure of Personal Information if anyone decided to use my Service. If you choose to use my Service, then you agree to the collection and use of information in relation to this policy. The Personal Information that I collect is used for providing and improving the Service. I will not use or share your information with anyone except as described in this Privacy Policy. The terms used in this Privacy Policy have the same meanings as in our Terms and Conditions, which are accessible at ShinStats unless otherwise defined in this Privacy Policy. Information Collection and Use For a better experience, while using our Service, I may require you to provide us with certain personally identifiable information. The information that I request will be retaine...

SQL Journey: Blog #3

I have reached the end of lesson 2. The final project is entitled "Data dig" where we are given a set of interesting data sets: NASA astronauts , Superbowl results , Pokemon stats , NBA players , Top movies , Top countries by population , Solar system objects by size , Marvel characters , Furniture store sales , Earned KA badges , Winston's donut logs , Card game results , and NFL draft picks . We are to pick one of those data sets and use advanced SELECT queries to discover things about the data. What sort of questions might one have about that data, like if they were using it for an app or a business idea? Here are some ideas:What are average, max, and min values in the data? What about those numbers per category in the data (using HAVING)? What ways are there to group the data values that don’t exist yet (using CASE)? What interesting ways are there to filter the data (using AND/OR)? Basically, the above given questions will serve as a guide on what we could dig from ...

SQL Journey: Blog #5

Let's do the challenge associated with the JOIN clause entitled, "Bobby's Hobbies". Instructions: Step 1 We've created a database of people and hobbies, and each row in hobbies is related to a row in persons via the person_id column. In this first step, insert one more row in persons and then one more row in hobbies that is related to the newly inserted person. I inserted the first female character that came to mind in one of my favorite romantic sitcoms. Code: INSERT INTO persons (name, age) VALUES ("Robin Scherbattsky", 32); INSERT INTO hobbies (person_id, name) VALUES (6, "reporting"); Step 2 Now, select the 2 tables with a join so that you can see each person's name next to their hobby. Code: SELECT persons.name, hobbies.name FROM persons JOIN hobbies ON persons.id = hobbies.person_id; ***A more better code is: SELECT persons.name AS person, hobbies.name AS hobby FROM persons JOIN hobbies ON persons.id = hobbies.person_id; but ...

Shin Nix

Search This Blog