Bronze layer · Learn Microsoft Fabric

Bronze layer

Hello!

I’m trying to figure out how to handle properly schemas drifts that may appear between the operational tables and the ones that I have stored in Fabric in bronze layer. For instance, in operational db I have a table with a column stored as INT, it gets synced in Fabric and by default it will be added as INT here as well. In operational the column changes to decimal but in Fabric without full schema overwrite (which I don’t want because its a heavy job) the column will be kept as int. Therefore I don’t have a valid ingestion process.

I thought of a dummy solution for this. To map each column as string in bronze layer therefore I don’t care what happens with the columns in operational, my job will sync as string the values. And only on silver layer when I clean up the data, to choose the types that I want further on.

What do you think about it? Do you use something similar? If not, how do you handle this issue on your project?

Thanks a lot,

Ecaterina

0 comments