Workbench 3 FAQs
What is Workbench?
Workbench is a Windows-based application that lets you upload data sources to Domo.
Can Workbench update or make any changes to our original data?
No, it does not modify your original data. Workbench is designed to read and transmit data to Domo. Workbench does let you modify the data going in to Domo through transforms, calculations, and joins.
What type of encryption does Workbench use to transmit data?
All data transferred from Workbench into Domo’s production systems is sent using encrypted HTTPS sessions, the same technology you typically use to conduct online banking and online purchases. No data is sent from Workbench to Domo in an unencrypted manner.
If access credentials cannot be stored as part of the Windows DSN, how are those credentials stored?
Workbench stores access credentials for ODBC data sources. To properly protect these credentials, Workbench uses industry standard AES-256 bit encryption. Workbench enforces encryption automatically so users do not have the opportunity of mistakenly storing their passwords or other credentials inappropriately.
How are access controls configured for Workbench?
Workbench is configured by the client from an access control perspective. Workbench allows users to upload data sources into Domo to enable KPI card creation and automated updates. Users select data sources (System DSNs, flat files, Microsoft Excel spreadsheets, JIRA, QuickBooks, XML namespaces) to which they already have access. Workbench can connect to data sources only if the Microsoft Windows system running the software can reach the data source, and if the machine has access to read the data source files or databases.
Is any of the data transmitted by Workbench cached on the local machine?
Workbench does not cache data sources. It reads data, normalizes it, and forwards it into Domo’s production infrastructure. Workbench saves configuration files and log files, but does not store, write, or cache data.
Do you support Windows 32 and 64-bit versions?
Yes, both 32 and 64-bit Windows versions are supported. For more system requirements information, see How do I install Workbench 3?
Are 32-bit ODBC connections supported?
Yes. Run the 32-bit version of Workbench after installing.
What is the maximum size of a data sources that Workbench supports?
Workbench limits uploading to 50 million rows for a single upload job. You can use a lastvalue variable to upload rows incrementally. For more information about query parameters, see Understanding the Workbench user interface.
You can check the size of your data by clicking Validate Data.
Can Workbench run from a command line?
Yes, Workbench can be executed directly from a command line and/or added as a task in an ETL package.
For more information about running Workbench from the command line, see Running Workbench 3 from the command line.
How can I improve the performance of a MySQL driver?
When using a MySQL driver, you can decrease its memory usage and improve its performance by configuring parameters for the DSN.
To configure your MySQL DSN,
When selected, the driver does not set packet limits for results.
When selected, the driver does not cache results and uses forward-only cursors.
Note: Workbench does not need anything other than "forward only" cursors and the MySQL ODBC driver performs better using the "forward only" cursors option.