First of all thank you for sharing with us your journey with SQL Mesh, it's helping a lot on-top of the official documentation thanks to many examples and comparisons.
I am still struggling about one point when thinking about virtual environment: wouldn't be a risk to have many physical snapshots of the same model ? I am thinking about working with big tables stored on cloud warehouse which requires to spend a lot of time to create a new physical copy of the table for dev.
Is there any smart thing done behind the scene by SQL Mesh to avoid n-plicating storage costs and compute costs to create the snapshot ?
First of all thank you for sharing with us your journey with SQL Mesh, it's helping a lot on-top of the official documentation thanks to many examples and comparisons.
I am still struggling about one point when thinking about virtual environment: wouldn't be a risk to have many physical snapshots of the same model ? I am thinking about working with big tables stored on cloud warehouse which requires to spend a lot of time to create a new physical copy of the table for dev.
Is there any smart thing done behind the scene by SQL Mesh to avoid n-plicating storage costs and compute costs to create the snapshot ?
Thanks!