Automating Tableau Extracts or Alteryx Workflows with Snowflake
Pitt's Snowflake data warehouse provides secure access to university data. In order for developers, SQL power users, and system integrations to extract data from the warehouse, they will need to create a programmatic access token (or automation token) .
An automation token provides technical users with the ability to access data when utilizing Pitt Passport is impossible. Automation tokens are created and managed by the Snowflake user, and must be rotated periodically. Users utilizing an automation token must connect from Pittnet or Global Protect. Upon request, Pitt Digital Analytics will grant a Snowflake user the ability to create an automation token. Contact the Help Desk and provide the username for the existing Snowflake user.
Automation tokens replace functionality previously offered through UDA4 accounts. UDA4 users should plan to move their workloads from Oracle to Snowflake using automation tokens. Contact the Help Desk to request a consultation on migration.
Additional information
Note: Automation Accounts (AA_) in Snowflake previously provided this functionality. Snowflake is deprecating the authentication mechanism that allowed Automation Accounts to work, so users must transition to automation tokens before August 2026.
Analytics Database Hosting in Snowflake
Alteryx and Tableau developers can take advantage of Analytics Database Hosting in Snowflake. The Analytics Database Hosting program allows analytics developers to store data specific to their responsibility center in Snowflake. Data from responsibility centers and the enterprise data sources can be combined via SQL to drive analytics value for your team. A schema is created in Snowflake to host the RC (or RC project) data, and users can be granted write access or read access to the data. Combined with an Automation Account, university developers have a flexible, governed platform for analytics workloads.
- Schemas are named with an R and the responsibility center code (e.g. R61). Analytics teams are encouraged to utilize the RXX base schema, though sub-projects can be created with the prefix and a project name (e.g. R61_OPERATIONS).
- Two "LAC - " prefixed groups will be created to govern access - one for read only to the schema, and one for creating and update tables. Access is then granted to CDS groups controlled by the responsibility center. This allows for collaboration and sharing of data, all within the control of local data analysts and RC administrators.
Analytics Database Hosting replaces the UDA4 database hosting. UDA4 users should plan to move their workloads to Analytics Database Hosting. Contact the Help Desk to request a consultation on migration.