1 of 1 people found this helpful
It is possibly not the best solution for users to be directly connecting to Tables as a lot of the times they will not have the experience or knowledge of tables and data structure.
The best practice for this kind of requirement is to join the required tables need for different kind for reporting.
You may join Department + Sales For Internal sales Analysis
You may join Customer + Sales for Customer Analysis
etc for the different sets of reporting needs
You should create the joins within tableau
Remove any unwanted fields
Rename any fields to make them more understandable user friendly
Add calculations for any common calculations
Once this data set is prepared.
Publish datasource to tableau Server with appropriate name.
Users should be connecting to these verified and published datasources
This will avoid people reporting the same KPI's differently as they will be working from same source.
Hope this helps
Nope Waseem. Tableau doesn't suggest any tables but If you drag two or more tables on the connection area, it will suggest the key columns that should be joined based on the similarly named column.
Creating your own datasources within tableau for use by multiple users is a good idea. I've often worked with clients who prefer to create views/custom tables within their SQL Server and point tableau at the view or table. It depends how "live" you want the data to be and how fast your database is.
Is it ok to create multiple data sources even though you are connected to the same database in SQL Server? A dashboard will need so many joins as per the need of worksheet...