In-Database standard tools
Browse In-DB Tool
Connect In-DB Tool
Data Stream In Tool
Data Stream Out Tool
Dynamic Input In-DB Tool
Dynamic Output In-DB Tool
Filter In-DB Tool
Formula In-DB Tool
Join In-DB Tool
Macro Input Tool
Macro Output In-DB Tool
Sample In-DB Tool
Select In-DB Tool
Summarize In-DB Tool
Transpose In-DB Tool
Union In-DB Tool
Write Data In-DB Tool
In-Database predictive tools
Frequently asked questions
Read privileges are required to access the underlying database.
Write privileges are required to create a table in the database.
The temporary tables are deleted at the end of the run. If Alteryx crashes while the Data Stream In tool is being run, then the next time that an in-database workflow is run, all temp files created by Alteryx in the database in the previous three days are cleaned out.
To allow visibility of a temporary table across sessions, Alteryx must create a permanent table that is eventually deleted at the end of a workflow. It is necessary to have CREATE permissions to stream in data from a database and write data to a database. The exception is Microsoft SQL Server.
The underlying rules are maintained during the process the same as with the database connections via the standard Input Data and Output Data tools. If there is a database timeout or if there is a limit to the number of queries per day that you can run, it will affect your connection to the database.
A SELECT statement is triggered by the Connect In-DB tool and additional queries are created by downstream tools and nested within this query. The addition of one of the following three tools completes the query and sends it to the underlying database: Write In-DB, Data Stream Out, Browse In-DB.
You can input your own SQL statement in the Query box for the Connect In-DB tool, which also gets embedded within the SELECT statement.
The SQL query for the underlying database is triggered at runtime for each Browse In-DB, Data Stream Out or Write Data In-DB tool.
The Browse Data In-DB tool can be configured to cache the data as a .yxdb file when the workflow is run.
Once the data is cached, if the workflow is re-run and the database connection or query (including the number of records to browse) has not changed, the query will not be re-run. Instead, the data will be pulled from the cache.
An output message indicates whether or not the data was cached. Clicking the link will open the data results as a .yxdb file in a separate window.
The in-database cache is used any time a workflow is re-run without changes to upstream tools. Making a change to any upstream tool will trigger a new query and a new cache will be created.
No, the “Browse first  records” option only limits the number of records displayed in the Browse In-DB tool. Other tools in the workflow will process the number of records that pass through at any given point.
The field has CLOB/LOB datatype and will not work with most of the comparison operators in the Filter or Formula tools. The error reflects that no columns are returned, even when the data matches the comparison. This is expected behavior with SQL and Oracle, as they do not support comparisons with LOB data