Anda di halaman 1dari 8
Improving Database Query Pecformance | Tableau Sofware + +ableau English © Products English fi) © Tableau Desktop Francais Deutsch Hi © Tableau Online 23201 Portugués © Tableau Server Espaiol © Tableau Mobile © Tableau Public ° Free Trials © Solutio: © Industries © Departments © Data Environments © All Solutions « Leaming © Training & Tutorials © Product Demos © Customer St © Visual Gallery © Whitepapers © Webinars © Events & Conferences ‘© Support Product Support Training Consulting Services Drivers & Activation Customer Portal Knowledge Base Community Forums Groups © Ideas © Partners © Academic Program Alliance Partners Reseller Partners OEM Partners Technology Partners © My Partner Resource Center © About hip tableau comiariclesiknow edgebasoldatabase-query-pexformance 82015 Improving Database Cer Pertarmance| Tatas Software Mission Leadership Careers Newsroom Blog . Investor Relations Contact Us Tableau yundation + Free Trial Knowledge Base Improving Database Query Performance Product(s): All Version(s): All Last Modified Date: 19 Mar 2015 Article Note: This article is no longer actively maintained by Tableau, We continue to make it availabl but some steps may vary due t produet changes. suse the information is sil valuable, At the heart of creating well-performing workbooks and visualizations is the basic principle that the visualization will never run faster than the underlying query. Therefore, to ensure a workbook is running as quickly as possible you need to ensure the query is running optimally. For the End User Below are some tips and pointers to help workbook authors understand if data access is a problem and some suggestions on what they can do to address it. Know what you are asking Often a problem with slow-running visualizations is that you have inadvertently created a query that retums a large number of records from the underlying table(s), when a smaller number of aggregated records would suffice. The time it takes the database management system (DBMS) to calculate the results, then stream the records back to Tableau can be significant. You can check this by looking in the lower-lefi comer of the Tableau Desktop workspace and looking at the number of marks. If this number is very large, you are potentially pulling a large amount of data from the datab; # Sales # Shipping Cost 68 marks 17 rows by 4 columns Ensure you are not including any unnecessary dimensions in your visualization - this will affect the aggregations in the database and increase the size of the result set. Use native drivers hip. tableau comiariclesiknow edgebasoldatabase-query-pecformance cxsz01s Iron Database Quy Pertxmence | elon Stare Tableau products include the ability to connect to a wide variety of data sources. Many of these data sources are implemented as native connections which mean Tableau has implemented techniques, capabilities and optimizations specific to these data sources. Tableau engineering and testing activities for these connections ensure they are the most robust Tableau has to offer. Tableau has additionally implemented the option to use the general-purpose ODBC standard for accessing data sources beyond the list of named options available when creating a new connection, As a publicly defined standard, many database vendors make ODBC drivers available for connecting to their databases. Tableau provides the option to use these ODBC drivers to connect to data. There can be differences in how each database vendor interprets or implements capabilities of the ODBC standard. In some cases Tableau will recommend or require you to create a data extract to continue working with a particular driver. There will also be some ODBC drivers and databases that Tableau is unable to connect to. If there is a native driver for the data source you are querying you should use this over the ODBC connections as it will generally provide better performance, Test with another tool A good way to determine if a slow workbook is being caused by a slow query is to test the same query in another tool, such as Microsoft Access or Microsoft Excel. To find the query being run, look in My Documents\My Tableau Repository\Logs and find a file titled log.txt. Open this file and scroll up from the bottom until you find a section like the following: 2011-08-04 13:46:16.161 (2198): DATA INTERPRETER: Executing primary query. 2011-08-04 13:46:16.171 (2204):

Anda mungkin juga menyukai