To better accommodate one of our larger customers, the icon view on the Overall Health tab has been improved to allow more servers to be shown at once.   There is also a new “condensed view” in the browser version of the VitalStatus database created for the same reason.

The Database Health module continues to be a work in progress.  Even after making changes in 10.9 to only refresh a databases’ default view, rather than all views, two very alert customers noted that VS was still creating view indexes of non-default views where they had not existed before.  After some intensive research we have found that just “looking” at a view to get its’ name–without calling view.refresh– will create a view index if it doesn’t already exist and this was causing disk space issues with those customers.

The database health has been modified to only refresh the inbox folder of mail files, and no other views.   I’d love some feedback on this.  Obviously looping through and refreshing all views is the best way to find if a database is corrupt, but the trade off is that it creates view indexes on views that had previously been discarded and this comes at a cost of increased disk space.    So let me know your thoughts– We may offer the option to loop through all database views in the future if requested.   For now though, we look specifically for the ($Inbox) folder and refresh that.  If the database doesn’t have such  a folder, we move on to the next db.

Tags

No responses yet

Leave a Reply