|
178 | 178 | GO |
179 | 179 | ``` |
180 | 180 |
|
181 | | -The basic idea here is...Grab the rowcount above and below a specific point in time. Since the table is insert only, this will tell us exactly how many records are inserted, vs cleaned up by the retention policy cleanup job. |
| 181 | +The basic idea here is...Grab the rowcount above and below a specific point in time. Since the table is insert only, this will tell us exactly how many rows are inserted, vs cleaned up by the retention policy cleanup job. |
182 | 182 |
|
183 | 183 | I ran the above proc every 5 minutes for a few days and then I ran this analysis query to see what it looked like: |
184 | 184 |
|
@@ -261,4 +261,4 @@ I thought it would be cool if I could inspect the actual contents of the columns |
261 | 261 |
|
262 | 262 | Well...after about 5 hours of pulling my hair out...I discovered that `sys.column_store_segments` contains a `min_data_id` and a `max_data_id` value, but for columns of type `datetime2` it's just the raw value, rather than a pointer to some dictionary value or something... |
263 | 263 |
|
264 | | -So my next blog post will likely be how I figured that out and my solution for it. I didn't want this post to be even longer than it already is 😂 |
| 264 | +So my next blog post will be about how I figured that out and my solution for it. I didn't want this post to be even longer than it already is 😂 |
0 commit comments