Enabling Workbench to read/recognize temp tables
Comments
-
Are you able to save the temp table into a format that could be easily uploaded via workbench? .CSV comes readily to mind here as a possible format for a workaround.
"When I have money, I buy books. When I have no money, I buy food." - Erasmus of Rotterdam0 -
@Giancarlo, did the above reply by nalbright help address your question?
0 -
So this problem is caused because Workbench is asking the database server for the schema, but the database server (SQL Server in this case) is returning an error that it doesn't know the schema of the query due to the use of the temp table. The error will look something like:
ERROR [42000] [Microsoft][SQL Server Native Client 11.0][SQL Server]The metadata could not be determined because statement 'INSERT INTO #temp1 SELECT 2 As Col' uses a temp table.
One workaround that I am aware of is to use T-SQL to explicitly specify the schema. So instead of:
SELECT 1 As Col
INTO #temp1
INSERT INTO #temp1
SELECT 2 As Col
SELECT Col FROM #temp1
DROP TABLE #temp1You could execute something like:
EXEC ('
SELECT 1 As Col
INTO #temp1
INSERT INTO #temp1
SELECT 2 As Col
SELECT Col FROM #temp1
DROP TABLE #temp1
')
WITH RESULT SETS (
( Col int )
)0
Categories
- All Categories
- 1.7K Product Ideas
- 1.7K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 294 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.8K Transform
- 97 SQL DataFlows
- 607 Datasets
- 2.1K Magic ETL
- 3.8K Visualize
- 2.4K Charting
- 707 Beast Mode
- 49 App Studio
- 39 Variables
- 667 Automate
- 170 Apps
- 446 APIs & Domo Developer
- 44 Workflows
- 7 DomoAI
- 33 Predict
- 13 Jupyter Workspaces
- 20 R & Python Tiles
- 391 Distribute
- 111 Domo Everywhere
- 274 Scheduled Reports
- 6 Software Integrations
- 115 Manage
- 112 Governance & Security
- Domo Community Gallery
- 31 Product Releases
- 9 Domo University
- 5.3K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 103 Community Announcements
- 4.8K Archive