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.4K Product Ideas
- 1.4K Ideas Exchange
- 1.4K Connect
- 1.1K Connectors
- 278 Workbench
- 4 Cloud Amplifier
- 4 Federated
- 2.7K Transform
- 89 SQL DataFlows
- 556 Datasets
- 2K Magic ETL
- 3.3K Visualize
- 2.3K Charting
- 569 Beast Mode
- 11 App Studio
- 27 Variables
- 579 Automate
- 141 Apps
- 414 APIs & Domo Developer
- 23 Workflows
- 1 DomoAI
- 28 Predict
- 12 Jupyter Workspaces
- 16 R & Python Tiles
- 351 Distribute
- 91 Domo Everywhere
- 258 Scheduled Reports
- 2 Software Integrations
- 92 Manage
- 89 Governance & Security
- 9 Product Release Questions
- Community Forums
- 42 Getting Started
- 28 Community Member Introductions
- 85 Community Announcements
- 4.8K Archive