SQL DB Schema Reference
These articles cover the SQL DB schema version 4, which corresponds to Server versions 2025.2. Servers using user-managed SQL DB use this schema. See the version crosswalk for info on Server to SQL DB versions.
Each Server instance stores information in 2 default databases:
AlteryxGallery Schema
The database for the Server UI part of your Server instance. Go to AlteryxGallery SQL DB Schema.
AlteryxService Schema
The service-layer database. Go to AlteryxService SQL DB Schema.
Server Version to SQL DB Version Crosswalk
Server Version | SQL DB Schema Version | alteryx_server.__MigrationHistory Record Count | alteryx_service.__MigrationHistory Record Count | Supported MSSQL Version for User-Managed Instances | Documentation |
|---|---|---|---|---|---|
2025.2 | 4 | 33 | 8 | MSSQL Server 2019 and 2022, Amazon RDS for SQL Server | See SQL DB Schema Reference for SQL DB Schema version 4 (2025.2). |
2025.1 | 3 | 26 | 8 | MSSQL Server 2019 and 2022, Amazon RDS for SQL Server | See SQL DB Schema Reference for SQL DB Schema version 3 (2025.1). |
2024.2 | 2 | 18 | 5 | MSSQL Server 2019 and 2022, Amazon RDS for SQL Server | See SQL DB Schema Reference for SQL DB Schema version 2 (2024.2). |
2024.1 | 1 | 13 | 1 | MSSQL Server 2019 and 2022 | See SQL DB Schema Reference for SQL DB Schema version 1 (2024.1). |
Note
While the Server Version to SQL DB Version Crosswalk table refers to schema versions as simple numbers (1, 2, 3…), these version numbers do not appear directly in the SQL database.
Instead, determine the schema verison by counting the records in these collections:
alteryx_server.__MigrationHistory(Gallery schema)alteryx_service.__MigrationHistory(Service schema)
Each record represents a specific schema change. Therefore, the number of rows in each table serves as a proxy for the schema version listed in the crosswalk reference.
Warning
When you access a newer database (for example, 2025.1) from an older Alteryx Service version (for example, 2024.2) will result in a migration log error similar to:
Too many migrations are already applied to database. We expect 18 or less, but found 26.
This error refers to the number of rows in the migration collections and indicates a version mismatch between the Service and the database.