Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit 2a2f02c

Browse files
quick fix
1 parent 29421b9 commit 2a2f02c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

‎_posts/2024-08-05-temporal-table-weirdness.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ Oh wait...yes they are.
1111

1212
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.
1313

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.
1515

1616
This isn't a recipe, click here if you want to skip the story: [Stats and findings](#stats-and-findings)
1717

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /