A Couple of issues that I've had with this approach are, that I need to truncate the target table/partition first, which can be affected by blocks and delays; another issue is that I need to be fully aware all the time that this approach is in place when adding indexes or doing any modifications to the table since both the staging table and the target table need to be identical. I've had processes break because me, or someone else added added an index unknowingly of the impact it would have on the data load process. Are there any workarounds for these issues?
Never thought about Partition Switching on Standard edition before SQL Server 2016 SP1 ! Very insightful presentation....
This was exactly what I needed. Thank you so much for the great tips and insight!
A Couple of issues that I've had with this approach are, that I need to truncate the target table/partition first, which can be affected by blocks and delays; another issue is that I need to be fully aware all the time that this approach is in place when adding indexes or doing any modifications to the table since both the staging table and the target table need to be identical. I've had processes break because me, or someone else added added an index unknowingly of the impact it would have on the data load process. Are there any workarounds for these issues?
Too much fun Kendra =)
Thanks. That was explained very well.
Just love your videos 😍
... veeerrryy interesting. this sounds like a very good approach ... Thank you ! signed : Burnt By SpRename_User
#TeamKendra