Welcome to Tableau Server & Online Admin Virtual User Group Meeting. My name is Mark Wu. I am your host and one of the speakers. Today’s session will focus on Tableau data server. We have three awesome speakers.
Our first speaker is Meredith Dicks who is Tableau Product Manager. Meredith will talk about Data Server Architecture - What is data server? What is Tableau’s intent for Tableau data server? What business problems that Tableau’s Data Server tries to solve? Our 2nd speaker is Tableau Zen Master Mike Roberts who spoke to this group a few months back about workbook performance. Today Mike will focus on Data server automation and show us some new cool stuff like updating custom sql, server and connection info automatically for multiple workbooks. I am always amazed by Mike’s creativities around Tableau server.
Myself will talk about how to leverage Tableau data serve for data governance. How to create data dictionary? How to achieve single source? How do setup permissions? I will also show you what is new for data server v10.
As a quick reminder, I am going to keep everyone mute during presentation. If you have any questions, pls feel free to use chat or Q/A panel. We will have some dedicated Q/A time at the end. With this, I will turn to our first speaker Mr. Dicks.
In TC15 Las Vegas, I was panel member with about 100 executive audiences. You guess, what is the most frequently asked question by those executives: Data Governance. How to avoid multiple versions of KPIs when you unlock your enterprise data? How to ensure Tableau self-service compliance with existing data governance process, polices and controls? Data gov is not ‘nice to have’ but ‘must have’ even for Tableau env. There are 3 layers to implement data governance for self-service tableau env. First at data warehouse layer, IT can mask all sensitive HR & Fed data data warehouse from database layer so we have piece of mind when Tableau desktop users to connect to data warehouse views. If your data warehouse has user entitlement table, you should be able to figure out how to leverage the user entitlement table to implement row level security. Initial query and data banding are two common approaches. Each has some limitations but they work. Second at Tableau server layer, use published data sources and let very few people to have edit access to published data sources. Then to have rest of workbook developer to have connector access but no edit access so you can achieve data governance. I w talk more for this in next slide. When you use your published data sources for others to consume, you can rename the field name more meaningful for others to understand, you can also put notes to let people know what is the field, where they come from, how they are changed so you can have your data definition at Tableau.
Then you need to have your process in placed to define roles and responsibilities for those who create Data source publisher and those who just create workbooks by using pds.
Let’s look into the Tableau & its related process layer.....
Published data sources are reusable connections to data. When you prep your data, add calculations, and make other changes to your fields, these changes are all captured in your data source. Then when you publish the data source to Tableau Online or Tableau Server, other people can use it to conduct their own analysis. This means you can offer a single source of truth at scale. Any changes to the data source relay to all connected workbooks.
What are the adoption challenges for published data sources? I see 3 challenges and I will talk about each other those: 1.Extra step permission setting 2. Lack of documentation or definition about PDS 3. Inconvenience
Tableau does not have so called Data Source Publisher role or Workbook publisher role. What Tableau as is only one site role as Publisher who can publish both data sources and workbooks.
Organizations normally have many data sources. You may just want to govern some of those many data sources. Governance does not mean to lock the data down but it means to let a few knowledgeable people have access. Those a few people have good data model knowledge and business process know-how, they can create joins & necessary calculations, then published the data as PDS or TDE or PDSX for others in the groups to create vizs. I am going to call those a few people as Data Source Publisher while the rest of business analysts as Workbook publishers.
Recording info and next meet-up session details will be all posted into this user group
Tableau Administrators User Group - Data Governance
Server & Online Admin TUG
Tableau Data Server Use Cases and Automation
1. Tableau Data Server Architecture - Meredith Dicks (Tableau
2. Data Server Automation - Mike Roberts (Zen Master)
3. Data Governance - Mark Wu (Co-owner of Tableau Server &
Online Admin TUG)
“Must have” for
Enterprise Data Management
Data steward vs workbook publisher
Published data sources
Mask sensitive data in data warehouse
Data entitlement table in data warehouse
1. How to avoid multiple versions of KPIs when you unlock your enterprise data?
2. How to ensure Tableau self-service compliance with existing data governance process,
polices and controls?
SSoT at scale
Less load to data source
Changes relay to all
Data Source Publisher
Site Role Publisher
• Data model
• Access to
• Can’t edit
Single Source of Truth
Published Data Sources =
Reusable & SSoT
Data Steward vs. Workbook
Meaningful field names and
comments as mini Data Dictionary
Version control data source v10 &
improved publishing workflow
Tableau 10 New Features for Server
Admin Webinar (TBD)
TC16 Austin Meetup - Server Admin User
Pls join server & online admin user group
to learn, share, and contribute everyday!