You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _posts/2024-08-05-temporal-table-weirdness.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ Oh wait...yes they are.
11
11
12
12
Just a small disclaimer: this post is not intended to be a technical deep dive into how SQL Server handles temporal table data retention policies behind the scenes. The intent is to just tell a fun story and maybe, hopefully, help out a future internet traveler that has also run into this issue and give them a bit of relief/clarity as to what's happening.
13
13
14
-
TL;DR / Spoiler: I couldn't figure out why my temporal history table kept reporting it had old rows. Turns out it was user error. Everything was working exactly as it should.
14
+
TL;DR / Spoiler: I couldn't figure out why my temporal history table kept reporting it had old rows, despite having a data retention policy set up. Turns out it was user error. Everything was working exactly as it should.
15
15
16
16
This isn't a recipe, click here if you want to skip the story: [Stats and findings](#stats-and-findings)
0 commit comments