Tracking Data Changes in C# .NET

In this session, I'm going to walk you through a capability that allows you to track data changes in your database with a single line of code. This capability is a powerful feature that comes out of the box with EF Core and offers APIs to enable engineers query historical data in their systems

here's some useful links:
Jeremy's Article about Temporal Tables:

Demo Code:

[bahtiyarozdere]

Eye opening! I have been working with Sql Server and dotnet since 2004. I had no idea there is this feature. We were building custom approaches instead. Thank you!

[christiantricarico]

Discovering your channel was a gift on this last day of 2022. Temporal table is a great feature.
I'm a .NET developer since 2006 and I really would like to share my knowledge with others and I really like your style. Hope to find the way in the new year 😀

[jwcodendaal]

Temporal tables are great. I use them when I can. One important note is it requires SQL 2016. In a lot of our CMS systems database compatability is quite old (pre 2016) and we tend to use triggers and audit tables for this kind of thing, very manual compared to temporal tables. Great video. Thanks.

[CodingsQT]

Super cool that you have a fundraiser attached to this! What an awesome way to give back to a meaningful cause.

[thanzeeljalaldeen]

this was what i was searching for a project im working on. i implemented this and most of the extra code we had to write was cleaned immediatly. this is great! thanks for the great insight!

[Tymonello]

Holy macaroni, that is so amazing. I've been doing that manually, with like one ID for db record, another ID to share between historical objects, and a flag IsHistorical, and while updating an object, then manually copying it, and adding a new one with edited data... this will save me lots of time!

Great video! I liked this feature because it's a clean way to track data changes. It helps you to keep your code less complex.

[lucabriguglia]

Exceptional! I used a kind of event sourcing approach to do basically the same. How on earth I did not know this was supported out of the box!

[mohamedeffat]

Is it just me or is this feature is so amazingly critical that I don't know how the majority of SQL databases I've seen out there live without it, interestingly Postgres does not (yet) officially support this feature.

I cannot get think of any business no matter large or small that would explicitly opt out of the history and protection this feature gives.

Thanks for the introduction to this 🙏

[hutchm]

Excellent information and thanks for sharing. I’m looking to potentially change what I have or use this for another application.

[minimalist_zero]

I had no idea something like this existed. Thank you very much for this.

[sherifezzat]

Oh my! This is amazing, brother! Let me share my experience with you! We have some old system that we had to code almost the same thing ourselves, by setting a trigger on the main table in DB on update to copy the old data from the main table to another history table i.e h_original_table_name, the history table contains old data, new data, user, hist_dt, and we used this to build a complete an e2e audit and traceability system, plus recovering from failures as you mentioned in the wonderful explanation! 👍 thanks ❤️

[BlazorPlate]

Wow! Why we didn't know about this until now. We are gonna apply this concept to our boilerplate SaaS template.

[E_G_]

This quick sessions&features are great to follow, thank you ☺

[shawn]

Lovely!! You are making my life easy, one line of code at a time..

[akshay_zz]

Saw two videos of yours. Learned two new things. Thanks

[mizanrahman]

This feature looks like Modified Trigger in SQL Server inserted and deleted table. Excellent job!.

[soucianceeqdamrashti]

This was a really good tutorial, learned a lot! Nice work Hassan!

[cdrbvgewvplxsghjuytunurqwfgxvc]

Thanks, and also for your work on odata!

[Ferenc-Racz]

Thank you for this video. Thank you for your knowledge sharing! I appretiate it.