I believe you're correct in that. However, according to the following link (which is what I have to go by because I've not instantiated either because it was simpler to build a handful of triggers with code that I wrote to make it easier), Change Tracking doesn't keep history (at least not "forever",if I'm understanding correctly), which I believe is what you need.
Here's the chart from that page that I'm talking about...
Don't get "history" mixed up with "Retention Period". My understanding is that there is no "forever" version of the "Retention Period".
To be sure, though, and to say it again, I've never used either because they both seemed too complicated or were missing something that I needed them to do (keeping indefinite history was one of them) and so I may have misread something along the line.
is pronounced "ree-bar
" and is a "Modenism
" for R
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
"Change is inevitable... change for the better is not".
"If "pre-optimization" is the root of all evil, then what does the resulting no optimization lead to?"
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)