We are upgrading to 6.1.2 and are looking for recommendations on cycling the smat files. In our testing, we have found that even a smat database search with 2 weeks of data is super fast. We were thinking maybe we wouldn’t need to cycle the smat files every day. I wasn’t sure if the file sizes would be a factor.
Also, there are now three files for each thread with the following extensions:
.smatdb
.smatdb-shm
.smatdb-wal
Do all three files need to matched together when cycling and arching much like the .idx and the .msg files must be paired together?
Thanks…
Tom Rioux