When you publish a workbook, you need to decide whether to embed the data sources in the workbook or publish them separately. When you publish a data source separately, the workbook’s local connection is replaced by a connection to the published data source. If the data source connects to an extract, this enables the workbook to show updates when the extract is refreshed.
The table below shows a few common points of comparison for the different types of publishing. It is not a comprehensive list, and these are generalizations. How these and other issues not listed apply to you might be specific to your environment.
|Published separately||Embedded in workbook|
Enables central data management and governance; avoids data source proliferation.
Each embedded data source has a disparate connection to the data.
Each has the potential to show something different than the other at any given time (and data source proliferation is common).
|Meant to be shared; becomes available for other Tableau users to connect to.||Data is available only inside the workbook; it is not available for other Tableau Desktop users to connect to.|
Extracts can be refreshed on a schedule. You need to set up only one refresh schedule for the extract, and all workbooks that connect to it always show the most current data.
Embedded extracts that aren’t refreshed can be useful for showing snapshots in time.
If you want to keep the data fresh, each workbook must have its own refresh schedule.
|Generally helps you to optimize performance on the server or site.||Performance might be affected when the server contains multiple workbooks that connect to the same original data, and each workbook has its own refresh schedule.|
Thank you for sharing.