Hi @shiki ,
Yes it should retain records from the past 7 days.
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0953365
For more info:
1. Table Rotation
As the name implies, Table Rotation just implements a way of storing a limited amount of data on a table based on several parameters.
This means oldest data in the table will be deleted at a certain point in time.
How is this really done?
If we take the example of syslog table (System Definition -> Table Rotations -> syslog), you will see the following:
- Duration: 7
- Type: Rotation
- Rotations: 8
- Table Rotations Schedule: shows syslog along with other 8 tables starting with syslog0000 to syslog0007
First each of these tables under the form syslog0000 are called shards (or subtables if you want).
Each of these shards will store 7 days of data and with 8 in total we will have roughly around 56 days of data in total in syslog (the base shard syslog is cleaned automatically on first rotation which means over time it has no data).
The Table Rotations Schedule will show what is the exact start (Valid from) and end (Valid to) of storing period for each shard.
Now, what are some of the advantages of this model:
- older data can be removed without impacting existing data being inserted/queried
- the whole table will grow only to a reasonable size
- when querying based on creation date, we might only look in one shard alone
What are some of the disadvantages of this model:
- queries that don't use a creation date (sys_create_on) will force an expensive UNION ALL query that can be very slow
Mark it as helpful and solution proposed if it serves your purpose.
Thanks,
Anand
