Best Way to Handle Archive Logs

[Anurag Tripathi]

I have recently introduced archiving on my instance. The Archival logs are increasing hugely and will soon need to be addressed. i am sure i am not the only one who has come across this so i just want to see what others have done to address this.

[Anurag Tripathi]

One thing i came across on wiki is

http://wiki.servicenow.com/index.php?title=Database_Rotation#gsc.tab=0

Can anyone clearly explain me the difference in table rotation and table extension?

Also if i add table extension on archive logs, will i have any issue restoring the record or something??

ctomasi   sergiu.panaite  

jbarnesciti b-rad

MVP Corner

[Chuck Tomasi]

Database or table rotation keeps a limited set of information (e.g. 3 months) available at any time. Let's call them month 0, 1, 2. As soon as you get to month 3, month 0 is dropped. The data is gone. I wouldn't recommend this with table or record archiving. It's good for throw-away data like ECC queue or sent/received email.

I have not used table extension in conjunction with table rotation so I cannot speak to it.

[Anurag Tripathi]

Thanks Chuck, this is exactly what my understanding was before i came across this scenario today and found there is something called table extension also.

Interestingly the following 2 tables are on extension not rotation

sys_audit

sys_email

and i don't thing this data is lost ever, like in the case of rotation.

[Chuck Tomasi]

Correct. sys_email is not rotated. It is one of the reasons we created the data archival option.

I think that answers you question since sys_email is already using table extension. Archiving on a table with table extension is fine.