Chad D Scott commented on Oct 4, 2010

Don't maintain unread marks

I looked into this today, and I think you would probably be OK not running compact. I think that instruction from Admin Help (that's where this information was pulled) was specified to ensure that the underlying database option gets set. That appears to be all that happens when you run compact after making the change or when running compact with the -U option, which does the same thing. I note that in 8.5.2, toggling the setting in database properties is sufficient to set the database property. I don't know if that has always been the case, though.

Gregg Bendtsen commented on Sep 16, 2010

Don't maintain unread marks

Can you provide additional information on this? When I mark this setting on a database that was maintaining unread marks, the unread documents count display on the database icon blanks out. Does that mean it is no longer maintaining unread marks? If so, do I have to compact it to make the property take effect? If I have to compact it to make the property take effect, it seems that there should be no visible indication or change in the application until compact occurs. Thanks in advance for your clarification.