Summary
Bobsled standardizes column names during data movement to remove special characters and adjust casing, ensuring columns load properly to each warehouse destination.
This standardization happens automatically as part of every transfer, so columns from your source arrive in the destination in a format that's compatible with the destination's identifier rules—without manual intervention.
Casing
Bobsled adjusts the casing of column names based on the destination type.
Patterns:
- Snowflake destinations: column names are cased as UPPERCASE.
- e.g.,
Column_1becomesCOLUMN_1
- e.g.,
- All other destinations: column names are cased as lowercase.
- e.g.,
Column_1becomescolumn_1
- e.g.,
Special characters and spaces
Spaces and special characters in column names are replaced with an underscore (_). Each special character or space is replaced individually, so consecutive special characters will result in consecutive underscores.
Patterns:
- Snowflake destinations: special characters are replaced and the result is uppercased.
- e.g.,
Revenue (in 000s)becomesREVENUE__IN_000S_
- e.g.,
- All other destinations: special characters are replaced and the result is lowercased.
- e.g.,
Revenue (in 000s)becomesrevenue__in_000s_
- e.g.,
Standardization at a glance
| Source column name | Snowflake destination | Other destinations |
|---|---|---|
Column_1 |
COLUMN_1 |
column_1 |
Revenue (in 000s) |
REVENUE__IN_000S_ |
revenue__in_000s_ |
TIP:
• Bobsled applies these rules consistently across all transfers and Sledhouse Tables, so downstream consumers can rely on predictable column naming.
• If you need to preserve original column names for reference, the source schema is always available in your transfer configuration.