EnsLib_HL7.Message retaining data after purge
As I was going though and trying to figure out why our CACHE.dat has increased in size over the past 18 days, I found that EnsLib_HL7.Message is still retaining messages dating back to 2014 even though we have our purge set to 10 days. Has anyone else experienced this?
Thanks
Scott Roth
The Ohio State University Wexner Medical Center
Yes, and just recently too.
You very likely need to run an index validation against Ens.MessageHeader.
NAMESPACE>Set sc = $System.OBJ.ValidateIndices("Ens.MessageHeader",,1,1)
Depending on the size of your database, it could take a while ... possibly weeks if you're in the multi-terabyte range. It has very little impact on performance, though. If you think it might take a while, you can create a task class and have it run non-interactively in Task Manager (that's what I did).
Once it's complete, your message purge should remove the old cruft automatically.