A T-SQL load to a warehouse fails on a data type mismatch. What do you do?
Why C is the answer
Align the source column with the target type
Fix the mismatch at the source or cast it explicitly during the load.
In detail
- A type mismatch is fixed by aligning source and target types.
- Decide how to treat values that cannot be cast.
Use case
An illustrative scenario, not a real incident.
A source sends dates as text, and a warehouse load fails. Casting during the load aligns them with the target column.
See it in different ways
flowchart TD
A["Monitor hub"] --> B{"Which item failed?"}
B -->|"Pipeline"| C["Activity error output"]
B -->|"Notebook"| D["Spark logs"]
B -->|"Capacity pressure"| E["Capacity Metrics app"]mindmap
root((Monitoring))
Activities
Monitor hub
Capacity
Capacity Metrics app
Warehouse
Query insights
Spark
Logs
Copy step
Run detailsflowchart LR S0["Load fails"] --> S1["Find the column"] --> S2["Cast or fix the source"] --> S3["Load again"]
Key point: Align source and target types.
Why the other options are wrong
- A. Delete the deployment pipeline stage
- A stage has no effect on the load.
- B. Add a shortcut to the failing table
- A shortcut does not fix a type.
- D. Change the workspace role of the user
- A role does not change a data type.