Alteryx Designer Knowledge Base

What to check when a workflow runs in Designer and not in Gallery    There are some common reasons why the same workflow may run correctly in Designer and have errors when running in Gallery or when saving to the Gallery. The errors often include references to file not found, unable to access or connect, permission denied, or unable to translate alias. This article will review general ways to resolve these errors.   Environment   Products: Designer, Gallery Versions: all versions    Causes for file not found errors   Cause 1: The missing file was not included in the workflow dependencies when saving the workflow to the Gallery.   Solution 1   When saving a workflow to the Gallery, click on Workflow Options, then Manage Workflow Assets. Make sure to check the files on your workstation needed to run the workflow. A copy of each checked file saves along with the workflow in the Gallery's database on the Alteryx Server.   Before saving a workflow to the Gallery, you can check what files are required for the workflow to run by going to Options > Advanced Options > Workflow Dependencies.   When saving, the assets checked in the Manage Workflow Assets screen should include any files and macros used in the workflow and other workflows called by Run Command Events or chained applications. When using multiple events or chained apps, include all workflows called after running the first workflow.     When saving a workflow to the Gallery with input files marked as dependencies, the input files are not updated. If the inputs are updated regularly, consider having these files on a shared drive accessible by the Alteryx Server instead.   To use data on a shared drive in a workflow, leave the files unchecked in the Manage workflow assets screen. Having the files unchecked ensures the use of the latest version of the data on the shared drive when the workflow runs, rather than a potentially obsolete copy saved to the database.   Cause 2: The path to the workflow or files cannot be resolved.   Absolute folder paths to a location on your local workstation should not be used, as it will not match with a folder path on the server.   For example, this input file is on the C: drive of my computer but it will not match a file on the Server once the workflow is saved to the Gallery.     Solution 2    In the Workflow Dependencies screen select one of these options: 1. A relative path to the location of the workflow or 2. A UNC path to a network driver shared with the Alteryx Server.   Relative path: Click the All Relative button for files on your workstation to change the dependency paths. When the files are in the same directory as the workflow (recommended) there will just be a dot in the folder location.     UNC path: Double click the path to see the Workflow Dependency Properties window. This may be needed to view the whole path.       Causes for unable to access or connect errors and permission denied errors    Cause 1: The Run As user in the System Settings does not have permission to access a file or database.   When a workflow runs from Designer, the credentials used are from Active Directory for the currently logged in user. When the workflow runs from Gallery, the credentials come from the Run As user set in the System Settings on the Worker Run As tab. By default, the Run As user is the Local System account on the Server. The local system account is not a domain account and may only have permissions to the local drives on the server, not files on shared drives.     Cause 2: The Alteryx Service does not have the permissions needed to run a scheduled workflow job.    The Alteryx Service also runs as the Local System account by default.    Solution for 1 and 2   Use a service account or another account with the needed permissions to resources used in Gallery workflows.   In the System Settings Worker Run As tab, check the option to Run as a different user and enter the account. If errors occur only when scheduling, go to the Windows Services screen, right-click the Alteryx Service, select Properties, and the Log On tab, then use an account with proper permissions.    Causes for Unable to translate alias errors   Cause 1: A User or System connection exists in the workflow that is inaccessible from the Gallery.      The Gallery is unable to access User and System connections created on a workstation. Also, the encryption used for the password in the connection string is only valid for the computer generating the connection. It cannot be copied and used elsewhere. To check the type of connections saved on your workstation, go to Options > Advanced Options > Manage Data Connections > and look for the Type column on the right.     There is a separate menu for In-DB connections here: Options > Advanced Options > Manage In-DB Connections. The Connection type field is right after the Data Source     Solution 1    Create connections on the Gallery, and then share with the users needing access. For ODBC connections, we recommend DSN-less connection strings because users are only required to install the proper database driver on their local workstation for the data connection to work in Designer. Afterward, the user can access the connection from the Saved Connections menu in Designer when building a workflow.   For In-DB connections, using a file type connection is a must for saving to Gallery. When saving the workflow to the Gallery, select Workflow Options, and include the connection file as a checked item in the workflow dependencies.    Cause 2: A workflow connection is obsolete.    Solution 2   Ensure valid connections for Gallery exist to external data sources and check the alias name assigned to the connections. Afterward, in Designer, go to Options > Advanced Options > Manage Data Connections and Select the Sync All button. Check to see if the validated connection is listed and use that connection in your workflow.   Cause 3: The Gallery connection was shared with a Studio or an Active Directory group instead of an individual user.   Solution 3   Share Data Connections with individual users and not to share with Studios or Active Directory groups due to known issues where data connections are lost.   Additional Resources:    How Workflow Credentials Work on a Private Gallery 

How To: Enable Microsoft Excel Binary, Excel Legacy, Access (accdb extension) for In/Out tools   The following formats may not be found in the "File Format" option in the In/Out tools and require a separate installation from Microsoft: Microsoft Excel Binary (.xlsb) Microsoft Excel Legacy (.xlsm) Microsoft Access (.accdb)   Note that these drivers do not come with our installation but from Microsoft Office or separate driver installation.   Prerequisites   Product - Alteryx  Designer   Procedure   To download the driver, go to https://www.microsoft.com/en-us/download/details.aspx?id=13255 Follow the instructions to download the installer.  Run the installer. After installation, you should be able to find the Excel Binary, Excel Legacy and Microsoft Access (.accdb) options in the Input Data tool and the Output Data tool.   

How To: Add Exception Handling to Oracle Pre or Post SQL   Exception handling may be needed so that a scheduled workflow continues even if a pre or post Oracle SQL statement has an error. Since PL/SQL currently is not supported in the SQL Editor, you will need to create a stored procedure for exception handling and call the stored procedure in the pre or post SQL section.   This example shows how to create a stored procedure that handles exceptions for a delete table statement when the table was previously removed and does not exist. (Oracle currently does not have an IF EXISTS option.)   Procedure   Adding a parameter for the table name is recommended so that one stored procedure can be reused for any table.   Note: You will need to create procedure permission on the Oracle database, contact a DBA if you are lacking this permission.    Use this format in your SQL editor for the stored procedure. Notice a space is added at the end of the SQL command ‘DROP TABLE ’ followed by || for concatenation and the parameter name used as a place holder for the table name.      Once the stored procedure exists on the database, you can reference it in the Pre SQL or Post SQL sections of the Input Data or Output Data Tool. Click on the Ellipsis button to open the section.      On the Stored Procedures tab, just highlight the stored procedure name on the left, and then in the Value text box, type in the table name surrounded by single quotes.     Alternately, you can call the stored procedure from the SQL Editor tab, using this format:     Additional Resources   Input Data Tool  Output Data Tool   

This article details different methods for connecting to an Oracle database from Alteryx. 

We are working diligently and intelligently on making connections to databases easier, more secure, and faster in Alteryx. Even when we can make the best possible experience for our users come to fruition, any user may still encounter some issues due to the use of third party drivers and/or the intricate communications between the database, driver, and Alteryx. To help to minimize those issues, Alteryx is tested with an abundance of "supported" databases and drivers that are proven to be compatible but, unfortunately, you just can't test every database and every driver out there. Our technical specifications page found here will show you those databases Alteryx supports, as well as the drivers we have tested and support with respect to each database. This does not mean Alteryx will not connect to a database or driver you do not see on this page (or links within the page), however, Alteryx can not support those databases and/or drivers if troubleshooting or setup is required.

Issue   When connecting to an OleDB Datasource using the either the Input Tool or the In-DB Tools, users can encounter the below error message :         Error opening connect string: Microsoft SQL Server Native Client 11.0: Login failed for user 'user1'.\28000 = 18456   Environment   Alteryx Designer Drivers : OleDB Providers for Microsoft SQL Server   Diagnosis   Usually, when testing the Data Connection through the OleDB "Data Link Properties" window they are able to successfully test the connection :     However the error message will persist from the canvas.   Cause   When mentioning a username/password combination in a connection string, they need to be extracted in the program calling for it. A parameter will need to be set and added to the string so windows remembers the credentials and they can be extracted in program.   Solution   Open the Driver's configuration "Data Link Properties" window Go to the "All" tab Identify the Persist Security Info parameter - at this time it should be set to False Double-click and on this parameter and set it to True Apply all the changes Run the Tool on Designer again   Additional Resources   How To: Connect to an OleDB Data Source Database Issues – Working with Alteryx Customer Support Engineers (CSEs)     As always, don't hesitate to contact us over at Customer Support if you run into any trouble.

How To: How Does Alteryx Handle Oracle Dates   The Oracle default data format is DD-MON-YY. However, additionally, different data formats can be set per session. While this might seem at first confusing it can be useful if understood properly. Alteryx Designer on the other hand uses  YYYY-MM-DD HH-mm-ss as the default date format and data containing dates imported from Oracle will show up converted into that date format.   Prerequisites   Product - Alteryx (Designer or Server)  Product - Third Party (Oracle Drive and connection to Oracle database). Supported versions.   Dates in Oracle and in Alteryx Designer   The Oracle default date format for input and output is  DD-MON-YY e.g. 01-JAN-19. It is controlled by the value of the NLS_DATE_FORMAT parameter. In other words the default value of NLS_DATE_FORMAT is:     DD-MON-YY     Please note that the date format can be set on database level, on instance level, and on  session level.   The below SQL queries will return information on the data format being used: Database level: SELECT * FROM nls_database_parameters WHERE parameter = 'NLS_DATE_FORMAT'; Instance level:  SELECT * FROM nls_instance_parameters WHERE parameter = 'NLS_DATE_FORMAT'; Session level:  SELECT * FROM nls_session_parameters WHERE parameter = 'NLS_DATE_FORMAT'; To modify the current session data format use the ALTER SESSION statement. This statement stay in effect until disconnecting from the database. For instance you can  use the below to change the session date format:     ALTER SESSION SET nls_date_format = 'dd/mon/rr'     On the other hand the default data format in Alteryx is YYYY-MM-DD HH-mm-ss.  Data columns of Date data type imported from Oracle into Designer will be displayed in Designer's default format. When filtering data of data type Date in Designer it is important to use the date format that is used in the underlying Oracle database even though the date format might be different from the one displayed in Designer.   Common Issues   When connecting to an Oracle DB filtering (in-DB) on date as displayed in the long format in Designer you might encounter the following error. Error: ORA-01861: literal does not match format string Browse In-DB (6) DataWrapOCI: Unable to prepare the query: "WITH "Tool1_ba3e" AS (Select * From HH_STORE_FILE), "Tool5True_799e" AS (SELECT * FROM "Tool1_ba3e" WHERE "DATE_COLUMN" = '2019-07-03 00:00:00') SELECT * FROM "Tool5True_799e" WHERE ROWNUM <= 100" Error: ORA-01861: literal does not match format string     This error message comes from the fact that internally, as explained above Oracle uses the  default date format DD-MON-YY to store the date. To solve the issue use in the Filter tool the Oracle default data format.   Additional Resources   Oracle Database Online Documentation: Setting up a Globalization Support Environment - NLS_DATE_FORMAT Oracle Database Online Documentation: ALTER SESSION

How To: Build Queries without using the Visual Query Builder   The Visual Query Builder window can take a long time to load because it always loads all column metadata for all tables for all schemas, even if a default database is selected in the database connection. This article will walk through using the In-Database tools as an alternative to using the Visual Query Builder.    Prerequisites   Alteryx A working Database connection This works best for connections supported for In-DB as noted in the Supported Data Sources and File Formats   Procedure   The Tables view loads only tables names and no column names for the default database selected and it caches the list. This allows it to load faster than the Visual Query Builder.   Make the Tables View the default view Drag an Input tool on the canvas and connect to a database (it doesn't have to be the database in question, any database will work) Click the Tables view and click the checkbox next to "Open Tables view by default" at the bottom left of the window  Create an In-DB Connection to your database as described here: How To: Create an In-Database Connection Use a Connect In-DB tool to connect to the database. To build your query: Select the table name in the Tables view. This creates a SELECT * FROM TABLE statement with no criteria to limit the query Use the In-DB tools to build the query. e.g. the Select In-DB tool to select only columns you need or the Filter In-DB to remove rows not needed Alteryx constructs a SQL query based on the tools on the canvas and sends it to the database In the example below, both workflows accomplish the same thing, one through the Visual Query Builder, one using the In-DB tools:   Additional Resources   FAQ: How Do the In-Database tools Work? How To: Create an Alteryx In-DB Connection File Database Issues – Working with Alteryx Customer Support Engineers (CSEs)

Amazon Redshift: Check 'stl_load_errors' system table for error details   When writing to Amazon Redshift, the following error appears:     Data Stream In (x): The COPY failed with error: [Amazon][Amazon Redshift] (30) Error occurred while trying to execute a query: [SQLState XX000] ERROR: Load into table 'ayx1XXX' failed. Check 'stl_load_errors' system table for details.     Environment   Alteryx Designer In-DB connection to Amazon Redshift   Cause   Amazon Redshift uses the stl_load_errors table to track errors that happen when loading data to a Redshift table. This table contains error messages that will provide necessary detail to determine the cause for an error.    For more information on the stl_load_errors table, see Amazon's STL LOAD_ERROR documentation.      Solution   Users with appropriate permissions can access the table themselves to investigate errors: Open a new Alteryx workflow. Drag an Input Tool on the canvas. Connect to the Redshift database. Go to the SQL Editor Window and enter the following query:    Select * From stl_load_errors   Run the workflow. The table will return an error code and an error reason. Use the column "starttime" to find the right error. See Amazon's STL_LOAD_ERROR documentation for a detailed explanation of all fields on the table and their load error reference for a list of errors.    Solution B    If the user doesn't have access to the table themselves, their DBA should be able to provide the same information.      Error Message examples   String length exceeds DDL length   Input data exceeded the acceptable range for the data type, try increasing the field size in Alteryx to resolve the error.  This often happens with multi-byte characters. In Alteryx, field size relates to characters, i.e.the value ' Góðan dag' only needs a field length of 9. In Redshift, field size is in bytes, to write out 'Góðan dag', the field size has to be at least 11.  See Amazon's document on Redshift character types for more information. Multibyte character not supported for CHAR (Hint: try using VARCHAR)   The CHAR datatype in Redshift only accepts single-byte UTF-8 characters. The VARCHAR datatype accepts multi-byte characters, to a maximum of four bytes. The WString datatype in Alteryx is translated into a CHAR datatype in Redshift. To load multi-byte characters into Redshift, use the V_WString datatype in Alteryx.      Additional Resources   STL_LOAD_ERRORS Documentation from Amazon Database Issues – Working with Alteryx Customer Support Engineers (CSEs)    

How To: format common ODBC DSN-less connection strings   Many people need to make ODBC connections to external data, but they may be unsure of how to format their connection strings, particularly with DSN-less connections. Here is a reference guide with examples of common DSN-less ODBC connection string formats. Here is a reference guide with examples of common DSN-less ODBC connection string formats. For connection strings not covered below, information can be found through the database or driver documentation or through online resources such as connectionstrings.org.   DSN-less connection strings help make workflows easier to export to other computers, as the importing computer does not need a matching DSN configured in the ODBC Data Source Administrator.   Prerequisites   ODBC driver for external data source such as SQL Server, Cloudera, or Hadoop    Products   Designer, Gallery   Procedure   DSN-less connection strings typically include: 1. the driver name, 2. server address, 3. database name or port number, and depending the authentication type, 4. user id and password.   Standard ODBC DSN Connection string format   odbc:DSN={DSN_Name};UID={Username};PWD={Password};   DSN-less example   odbc: Driver={SQL Server Native Client 11.0}; UID={Username}; PWD={Password}; DATABASE={Database_name}; SERVER={Database_Host}   DSN-less trusted connection, the id and password are taken from the driver configuration   odbc: Driver={SQL Server Native Client 11.0}; DATABASE={Database_name}; SERVER={Database_Host}; Trusted_Connection=yes   ODBC Connection string formats for Hadoop and Cloudera platforms   There are separate Hadoop and Cloudrea platforms and one where both are combined into one. These platforms use the same ODBC driver types: Hive (data warehousing), Impala (massively parallel processing), and Spark (performance based processing).   For DSN connections there is only parameter: DSN=[DataSourceName] (that's it).    In DSN-less connections for Cloudera and Hadoop, the driver, host, and port are all included in the connection string along with the authentication mechanism.   The authentication mechanisms for these driver types are the same (AuthMech in the connection string). 0 = No Authentication 1 = Kerberos 2 = User Name - the UID may be omitted with anonymous login enabled 3 = User Name And Password   No Authentication   Driver=Simba Hive|Impala|Spark ODBC Driver;Host=[Server]; Port=[PortNumber];AuthMech=0;   Kerberos   Driver=Simba Hive|Impala|Spark ODBC Driver;Host=[Server]; Port=[PortNumber];AuthMech=1;KrbRealm=[Realm]; KrbHostFQDN=[DomainName];KrbServiceName=[ServiceName];   User Name   Driver=Simba Hive|Impala|Spark ODBC Driver;Host=[Server]; Port=[PortNumber];AuthMech=2;UID=[YourUserName];   User Name and Password   Driver=Simba Hive|Impala|Spark ODBC Driver;Host=[Server]; Port=[PortNumber];AuthMech=3;UID=[YourUserName]; PWD=[YourPassword];   Optional parameters that may need to be added to a connection string if configured are: ServerType, SSL, and ThriftTransport.   Common Issues   If all the correct values for a connection string are not known, errors with the connection occur. In Designer, check the Results window and Engine log for details. For scheduled workflows, the Service log may be helpful, as well as the Gallery log if the workflow is running from the Gallery. A local system administrator may be needed to verify correct the parameters for the connection string. Here are the default locations for Alteryx logs, check your System Settings if the logs are not found. %ProgramData%\Alteryx\Engine logs %ProgramData%\Alteryx\Gallery\Logs %ProgramData%\Alteryx\Service Additional Resources   Connection Strings is a great resource with a thorough list of connection string formats for Oracle, MS SQL, PostgreSQL, and Teradata (others as well). Simba Hive ODBC Install Guide  Simba Impala ODBC Install Guide  Simba Spark ODBC Install Guide Troubleshooting Database Connections  Data source name not found and no default driver specified errors 

How To: Tell a Database connection type at a glance   Below is a quick overview of how the different types of database connections appear within "workflow dependencies." This will help determine and compare different connection types from a quick glance.   Prerequisites   Product - Alteryx Database connection(s)   Procedure   To view connections in the Workflow Dependencies, go to Options > Advanced Options > Workflow Dependencies. (The same notes apply for connections viewed through the Input/Output tool configurations except for the Gallery Connection).     1. Saved Data Connection Saved Data Connections can be recognized by the aka: at the beginning of the Connection String. They include all connections the user created through Options > Advanced Options > Manage Data Connections as well as Oracle and SQL Server connections created through the "Quick Connect" option. Also see https://community.alteryx.com/t5/Alteryx-Designer-Knowledge-Base/Database-Connections-Creating-an-alias-and-the-advantages-of/ta-p/15836 Saved Data Connections are saved in xml files on the user's machine with passwords encrypted. %AppData%\Roaming\Alteryx\Engine\UserAlias.xml contains user connections and %ProgramData%\Alteryx\Engine\SystemAlias.xml contains system connections.   2. In-DB Connection In-DB Connections show the connection name the user picked when setting up the connection. All In-DB Connections are saved with encrypted passwords either in %AppData%\Roaming\Alteryx\Engine\UserConnections.xml for user connections or %ProgramData%\Alteryx\Engine\SystemConnections.xml for system connections.    3. In-DB Connection using a file In-DB connections using files point to the file storing the connection information. You can recognize these by the file extension .indbc. They also include the path to the .indbc file.   4. Gallery Connection Gallery connections are created by the Gallery admin and then shared with the user so they can use them on their local machine. They start with aka: like regular saved data connections. When viewed in the Input tool, you can see the connection name. In the workflow dependencies they show up as the key used to identify them in MongoDB.    5. DSN-less ODBC Connection Any connection using an ODBC driver starts with the keyword odbc: For a DSN-less connection, all relevant connection information is stored in the connection string.    6. ODBC w/DSN An ODBC connection using a DSN on the user's machine starts with the keyword odbc: then points to the DSN name. Additional parameters may be added to the connection string, such as username and password, they will override the information for the connection parameters stored with the DSN.    7. OleDB Connection An OleDB connection starts with the keyword odb: and contains all relevant connection information in the connection string. When selecting OleDB as the connection option in Alteryx, a wizard helps build the connection string.    8. Oracle OCI An Oracle OCI connection starts with the keyword oci: and requires a tnsnames.ora file.  By default, the  tnsnames . ora  file is located in the ORACLE_HOME/network/admin directory.   9. 32-bit Connection 32-bit connections can be made as long as a 32-bit driver is available (For ODBC, OleDB, Oracle clients). They can be recognized by the 32bit: keyword BEFORE any other keywords indicating the type of connection to use.    10. (SQL Server) Bulk connection Bulk connections have their own prefixes to let Alteryx know to expect a bulk connection, e.g. ssvb indicates a SQL Server Bulk Loader connection. They may have additional parameters added to the connection string.       Additional Resources   How To: Connect to an OleDB Data Source Connecting to an ODBC Datasource How To: Create an In-Database Connection

Too much connection data for an OCI driver may cause an OCIEnvCreate Error   An OCI error may occur when running a workflow from a network location with many OCI inputs: OCIEnvCreate Error: No error handle available to report exact OCI_ERROR.   Prerequisites   A Designer workflow with Input Data tools having OCI connections to an Oracle database.   Product - Alteryx Designer downloads.alteryx.com Product - Oracle Instant Client for validated versions see: Supported Data Sources Oracle download site: Oracle Instant Client downloads   Procedure   Decrease the total connection data that OCI driver in the Oracle Client has to process for the workflow. If the workflow is accessed from a network drive, try putting the workflow in a folder close to the root of the driver, rather than in a long folder directory, or move the workflow to your workstation instead of a network directory. If there are many OCI connections in the workflow, see if the same data could be imported with fewer connections.   The OCI driver is recording the network location of the workflow. Also, if the workflow contains multiple OCI inputs, the Oracle Client OCI driver appears to compile all of them together to create the workflow connections.    Common Issues   A maximum limit of connection data for an OCI driver can be reached In testing, we found that a maximum limit of connection data could be reached, and then the error would occur. The workflow would run fine with multiple OCI connections if the workflow was located on the workstation. However, when running the same workflow from a network drive, the length of the folder path would determine whether or not it would error out. Similarly, adding or removing more OCI inputs would have the same effect. A limit would be reached, and an error would occur beyond that limit.    Additional Resources   Oracle Call Interface Programmer's Guide OCIEnvCreate()  

How to find the relevant information and configure a Databricks connection through the Manage In-DB Connections window. The Databricks connection includes bulk loading capabilities that allow users to load large data sets faster. 

Handling NULL Values in Databases In relational databases a NULL value is used to represent a missing or unknown value in the column. The ANSI SQL-92 specification defines the handling of the NULL value in databases.      SQL Ternary Logic SQL relies on a three valued logic. Additionally to true and false logical expressions can also yield unknown.  This is a consequence of SQL's support of NULL to mark either absent or unknown data. Thus, if NULL is part of a logical expression the outcome will be NULL. In more colloquial terms NULL means "it could have any value".   Therefore, in all the below cases the result will be unknown:   NULL = NULL NULL = 1 NULL <> 1 NULL > 1   Please note that the SQL standard does not specify how NULL values should be ordered in comparison with non-NULL values.   Testing for NULL From the above it emerges that a specific SQL command is needed to check whether a value is indeed NULL. SQL has the <expression> is null and <expression> is not null expressions to ascertain an expression is NULL or not.   The SQL standard also defines an expression to compare two NULL values treating them the same. However, not all SQL flavors support it and may instead have their own proprietary alternative. The SQL standard specifies <expression> is not distinct from <expression>.   Where and Having Clauses A Where clause needs to be true for the SQL query to execute.  Therefore if the condition in the Where clause will evaluate to unknown it will reject all rows. For instance   SELECT c_columns FROM t_table WHERE c_columns = NULL   will reject all columns. In order to use NULL in Where clauses WHERE c_columns is NULL should be used instead.   It is important to note that since NULL is neither true nor false, but rather unknown in SQL logic the below query will never return NULL values.   SELECT c_columns FROM t_table WHERE c_columns = 'ANY VALUE'   Additional Resource   Handling Null Values - Microsoft help documentation 

No Lua script was found   When reading in from a database, the following message is seen:   Info: Input Data (n): No Lua script was found for corresponding ODBC driver.   Environment   Alteryx Designer 2018.4+ Windows Operating System ODBC database connection     Cause   This message indicates that you are connecting to a database, and no Lua script was found. This is expected when you are connecting to a database that does not work out of the box with Alteryx. Please note this is a message and not an error or warning; it will in no way prevent your workflows from executing successfully if you are not using a custom Lua script.     Explanation To support new ODBC drivers that Alteryx has not validated/tested, you can create a custom Lua script that will map driver and database data types to Alteryx types.  To learn more about this (and find sample Lua scripts) please see the documentation Customizable ODBC Driver Connections found in: %LOCALAPPDATA%/Alteryx/bin/RuntimeData/ODBC

"Unable to find connection 'x' " when workflow is scheduled   When running a workflow via the Scheduler (for Designer with Automation), the following error is observed:   Unable to find connection "x"   Environment   Alteryx Designer Designer with Automation Windows Operating System In-Database Connection   Diagnosis   1. Confirm that you are using Designer with Automation and not Alteryx Server. You can confirm this by opening the Alteryx System Settings from Designer under Options > Advanced Options > System Settings. On the Setup Type page you will see Designer and Scheduler Only selected.   2. Confirm the In-Database connection is setup as a User connection. You can check this from Designer by navigating to Options > Advanced Options > Manage In-DB Connections and choosing the Data Source and Connection name you are using. It will show next to the name of the Connection:     Alternatively, you can check in the drop-down for the Connection Name Connect In-DB tool or the Data Stream In tool:       Cause   The In-Database connection in use is a User connection; scheduling requires a System connection or a File connection.     Solution A - System Connection   Follow the steps in this article to set up a System connection: How To: Create an In-Database Connection This will require admin permissions. Please see the following article for more information: Unable to create System Connection/System Connection type missing   Solution B-  File Connection   Follow the steps in this article to set up a File connection: How To: Create an Alteryx In-DB Connection File The .indbc file will need to be available to the Run As User or the user running the Alteryx Service. To avoid any issues, you can package the workflow, then schedule as follows: Package the workflow by going to Options > Export Workflow, making sure you check the box to include the .indbc file Go to Options > View Schedules On the Workflows tab, click the + icon Navigate to the .yxzp file you created above and set the schedule frequency     Additional Resources   Database Connections: Creating an alias and the advantages of using an alias Database Issues – Working with Alteryx Customer Support Engineers (CSEs)

Hive ODBC can be slow when writing to tables. If you are looking for a faster option to write to Hive and want to create a new table or overwrite an existing table, use the  IN-DB tools   to output your data. 

Alteryx has the ability to connect with MIT Kerberos based Impala implementations. With this feature, came the need to tell the Simba Impala driver that you are using Windows Kerberos and not MIT's version.

How To: Create an In-Database (In-DB) Connection   Apart from making standard database connections, which allow for data to be pulled from the database directly into Alteryx, Designer also has In-Database functionality. The In-Database tools allow for the workflow created to be converted into a query which will then be executed on the database, and not locally in Designer.     Prerequisites   Alteryx Designer Windows Operating System   Procedure   In Designer, drag and drop the Connect In-DB tool (located in the In-Database tool palette) onto the canvas Select the “Manage Connections…” option to establish a new In-DB connection The Manage In-DB Connections window should appear. To configure this window: Select the Data Source/Database type from the Data Source  drop-down. Under Connection Type, select User, System or File connection. For file connections, see this article: How To: Create an Alteryx In-DB Connection File If you do not see the System option available, see this article: Unable to create System Connection/System Connection type missing Under Connections, select New. Under Connection Name, enter a name for this connection. Under Driver, select the method of connection to use. Click the Connection String drop-down. You can choose to use an existing connection or create a new connection by clicking the New database Connection… option. You can also paste in the full connection string if you have it available. Repeat steps 5 and 6 for the Write tab. Click OK. If the connection was successful, the Choose Table or Specify Query window should appear.   The connection will now be stored in the Connection Name drop-down.     Additional Resources   Troubleshooting Database Connections FAQ: How Do the In-Database tools Work? Database Issues – Working with Alteryx Customer Support Engineers (CSEs)  

Issue   I am trying to set up a System alias, but the System option is missing.   Standard Connection - System connection is missing from Options > Advanced Options > Manage Data Connections > Add Connection    In-DB Connection - System connection is not an option:     Environment   Alteryx Designer Windows Operating System   Cause   The Designer is not running Elevated (aka running as an Administrator). Alteryx must be run with elevated privileges in order to be able to create a System Connection within Alteryx.      Solution   Right click on the Alteryx program (or on the Alteryx icon on your Desktop) and choose Run as administrator Please contact your IT department if you are unable to run Alteryx as an administrator     Additional Resources   Creating an In-Database Connection Database Connections: Creating an alias and the advantages of using an alias Database Issues – Working with Alteryx Customer Support Engineers (CSEs)