Tableau Joins vs Relationships: A Comprehensive Comparison

Поділитися
Вставка
  • Опубліковано 19 кві 2023
  • Tableau is a powerful data visualization tool that allows users to create insightful dashboards and reports. One of the key features of Tableau is its ability to combine data from multiple sources using joins and/or relationships.
    In this video, we'll explore the differences between Tableau joins and relationships, and when you should use each one. We'll start by discussing how Tableau defines joins and how they can be used to combine data from different tables based on a common field.
    We'll do this using Excel and I'll take you step by step, line by line on what Tableau is actually doing underneath the hood.
    ************************************************************************************
    JELLYMAN WEBSITE IS LIVE!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    For Comprehensive Tableau Training for Beginners to Advanced, visit JELLYMAN EDUCATION at
    jellyman-education.thinkific....
    There are 6 courses available which cover everything you need to know about Tableau Desktop from Beginners to Advanced users and also includes Tableau Online/Server and Tableau Prep.
    Hundreds of videos and near 50 hours of content await enthusiastic students ready to take on the next challenge in their Analytics Career.
    1) Getting Started with Tableau:
    jellyman-education.thinkific....
    2) Tableau for Beginners:
    jellyman-education.thinkific....
    3) Tableau for Intermediates:
    jellyman-education.thinkific....
    4) Tableau for Experts:
    jellyman-education.thinkific....
    5) Tableau Online:
    jellyman-education.thinkific....
    6) Tableau Prep:
    jellyman-education.thinkific....
    Lastly, the subscription model of the site means you get access to all current and future content. No need to buy individual courses or packages like other sites.

КОМЕНТАРІ • 33

  • @PythonArms
    @PythonArms Місяць тому +1

    as an experienced tableau dev you explain this very well. love your videos. well done!

  • @jamiyana4969
    @jamiyana4969 12 днів тому +1

    OMG EXACTLY WHAT I NEEDED!! 🥺I'm preparing for my internship (customer insights analyst) these days and found this channel. Do you have any good advice or study/practice source for someone in this field? thank you Sir!

  • @sudeshnasen6714
    @sudeshnasen6714 8 місяців тому +3

    Excellent explanation !!! Thanks a lot ! 😊

  • @AchilleMo
    @AchilleMo 2 місяці тому

    Super clear explanation, thx!

  • @hemaprakashp5268
    @hemaprakashp5268 3 місяці тому

    Hi Jed, good day! do you have any videos on tableau data modelling using Azure SQL data source. i am looking for scenarios like created the relationship between One Fact table to multiple dimension tables using primary key and foreign keys. thanks in advance!

  • @morninglory8988
    @morninglory8988 Рік тому +1

    Great explanation

  • @tableauuser
    @tableauuser Рік тому

    Hi, hope you have had a wonderful day so far. I have a question. I’m a freelance data analyst, and I have a client I made a report for him. I would like to know how to add him as a user to see his words on his website. Currently, he does not have a Tableau account. I have a meeting with him tomorrow, and I would like to know in advance

  • @Gatitdone
    @Gatitdone 8 місяців тому

    Thank you sir

  • @zhikailiang6676
    @zhikailiang6676 14 днів тому

    THANK YOU

  • @razzakahmad8731
    @razzakahmad8731 10 місяців тому

    I understood the point about aggregation being done internally (and without any potential error) by tableau when using relationship over joins. But what if i make the different join instead of the ones you made. i think you made left join on those tables that is why the aggregation changed from the actual ones so instead i could do the inner join using colour as key constraint and the aggregation will still be the same as what tableau does using relationships. My point is what is the need of relationships if i can achieve the same results using the appropriate type of joins?

    • @Superball90001
      @Superball90001 10 місяців тому

      The point of relationships is about Tableaus most common user. Tableau works great when there's a perfect data model set up but a lot of times that's not the case, and business people / project manager types will struggle with the concept of joins. Relationships will solve the problem for them 99% of the time.
      I'm not super happy about relationships because I just got burned by them myself. In fact I think they will hurt anybody that isn't working with sales data like in this example, because relationships are inner joining behind the scenes which isn't made explicit to us....

  • @maximillianquaife-larsen3799
    @maximillianquaife-larsen3799 4 місяці тому

    Thank you

  • @saikumareppakayala
    @saikumareppakayala Рік тому +2

    When to go for Joins and Relationships?

  • @Fujit_01
    @Fujit_01 Рік тому

    Thank you Jellyman for the explanation!
    I have a question please: I work at a data analysis consulting agency and we want to start using tableau to build dashboards for our clients, the problem is that when it comes to sharing the dashboard we can't upload it to tableau public because the data is sensitive, if we go with the tableau online option we need to have a creator license (we already have it) but the problem is that the client also needs to pay for a viewer license to view the dashboard, we can't ask our clients to pay for that and we can't pay for it as we work with multiple clients and we need to buy a license for each one of them. Is there a solution please?
    Thank you!

    • @jellymaneducation6168
      @jellymaneducation6168  Рік тому

      Unfortunately, theres no way around buying individual viewer licenses. From a security perspective, you really don't want to skimp on Online licenses. It gives you the ability to control permissions and access to ensure clients only see what they need to and can't see other clients work.
      I guess it also depends on your client structure. If you only ever have 2-3 clients at a time, you could always recycle licenses. One drops off then you give to the next client.

    • @Fujit_01
      @Fujit_01 Рік тому +2

      @@jellymaneducation6168 Thank you so much for your answer, recycling licenses seems like a good approach!

  • @vrriedo9827
    @vrriedo9827 11 місяців тому +1

    Great! Very good explanation 🥰

  • @isabellegfer
    @isabellegfer Рік тому +3

    Thanks! This is the best explanation I've seen so far for this subject.
    I have a question: I have a dataset that I need to refresh through Tableau Bridge. When I do it with JOIN the update runs perfectly but the calculation values are incorrect, when I do it with Relationship the values are correct but the update fails. Do you know if it is possible to update data set with relationship with Bridge? What could I be doing wrong?

    • @jellymaneducation6168
      @jellymaneducation6168  Рік тому

      Currently eating Korean Fried Chicken! Will answer when I get home 😆

    • @isabellegfer
      @isabellegfer Рік тому

      ​@@jellymaneducation6168 Just thought you probably were sleeping right now haha Korean food is great, I can wait :)

    • @jellymaneducation6168
      @jellymaneducation6168  Рік тому

      Hey Isabelle, to be honest I've never heard this problem before. Therefore, my approach would be to do some systematic testing.
      1. Is Tableau Desktop to blame or Tableau Bridge? You can test this by creating a brand new workbook with a very simple Excel data set. Repeat what you've done and see if the error still occurs. If it still occurs then most likely its Bridge. If it doesn't occur, it's your workbook.
      2. Secondly, recreate a simplified version of your workbook from scratch and test that as well.
      In rare cases, the software does bug out and a single workbook becomes faulty in which case you need to built it again from scratch.
      However, this has only really happened to Mr a handful of times.
      Hope this helps

    • @isabellegfer
      @isabellegfer Рік тому +1

      ​@@jellymaneducation6168 Hello. Thank you for replying.
      I created a new very simple data source (only two CSV connecting each other with relationship), published it to the Server and tried refreshing it with Bridge - didn't work.
      I can not attach the error message where but it says "Could not refresh the data source, if the issue persists, contact Tableau Support".
      When I click to see the details, it opens a box for me to select again the files on my computer - I do so, which really helps when I execute this process on the Data Source made with JOIN, but on this relationship one it doesn't help.
      Any ideas? Or maybe Bridge is just not supposed to work with DSs that use Relationships.
      Thank you!

    • @jellymaneducation6168
      @jellymaneducation6168  Рік тому

      Are you publishing the data source first prior to the Dashboard?

  • @AmitGrg_Rakhali
    @AmitGrg_Rakhali 3 місяці тому

    Great explanation! and I loved your Guitar Collection! :)

  • @sa34w
    @sa34w 3 місяці тому +1

    Which has more performance ? Joins or Relationships?

    • @jellymaneducation6168
      @jellymaneducation6168  3 місяці тому

      Depends on the situation. Generally speaking I would say relationships and the only reason I say that is because the connection occurs when the visualisation is created; not before. Therefore, for specific visualisations where you only use one of the sources, it uses the table directly.
      That being said, it really depends on the situation. I've seen it go both ways.

  • @Finneous101
    @Finneous101 Рік тому +1

    I'm not trying to be mean, but I think you explained your message clearly, but this still didn't make sense overall. I like your videos usually, but this one left me scratching my head.