Domo workbench - "attempting to open data source"
When a workbench job is executing, does anyone know what is happening when the preview window execution step says "attempting to open data source"? We will have a job that gets stuck on this step for several hours and it is unable to get past this step, then the query times out. The workbench job is executing a stored procedure in our sql server database
Answers
-
It's attempting to connect to the database but running into connection issues. Are you able to get a response from the server that's hosting the data source? Are you behind a firewall that would restrict access?
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**0 -
I have asked the firewall question to someone with more knowledge than me, but I do know the we have other workbench jobs set up on the same database/server that are connecting and running successfully.
This job that is giving us the "attempting to open data source" struggles has done this many times in the past. It is a very massive stored procedure (425 columns, 1.8 million rows) and typically takes 1.25-2.5 hours to run. We know that the width of this stored procedure is causing us problems in general, but I just don't know if that would have anything to do with the "attempting to open data source"0
Categories
- All Categories
- 1.2K Product Ideas
- 1.2K Ideas Exchange
- 1.4K Connect
- 1.1K Connectors
- 273 Workbench
- 2 Cloud Amplifier
- 3 Federated
- 2.7K Transform
- 78 SQL DataFlows
- 525 Datasets
- 2.1K Magic ETL
- 2.9K Visualize
- 2.2K Charting
- 437 Beast Mode
- 23 Variables
- 513 Automate
- 115 Apps
- 390 APIs & Domo Developer
- 8 Workflows
- 26 Predict
- 10 Jupyter Workspaces
- 16 R & Python Tiles
- 332 Distribute
- 77 Domo Everywhere
- 255 Scheduled Reports
- 66 Manage
- 66 Governance & Security
- 1 Product Release Questions
- Community Forums
- 40 Getting Started
- 26 Community Member Introductions
- 68 Community Announcements
- 4.8K Archive