A view index is an internal filing system that is used to build the list of documents to display in a database view or folder. By default, view indexes are updated on a server at scheduled intervals. To update a view index immediately after documents change instead, enable inline view indexing. When you enable inline view indexing, a critical view is always kept up-to-date for your users.

Enabling inline view indexing with the Updall task
You can enable inline view indexing with the Updall task which updates the$Index view design element. With this method, inline view indexing is enabled automatically in replicas of a database. In addition, if you enable inline view indexing in a design template, the inline view indexing is enabled automatically in databases that inherit their design from the template.

Enabling inline view indexing with INLINE_VIEW_INDEX setting
You can enable inline view indexing with the NOTES.INI settingINLINE_VIEW_INDEX. With this method, you specify a list of databases on a server to enable for inline view indexing. Unlike the Updall method, this method does not update the$Index view design element in databases and so does not propagate view indexing through replication and design inheritance.

Setting index expiration for inline view indexes
Use NOTES.INI settings to control when inactive view indexes expire and are flushed out of memory.

Using console commands to manage inline view indexing
Use server console commands to monitor and manage inline view indexing.

Showing inline indexing statistics
Use the show stat database.inline* console command to show statistics about inline indexing on a server.

Disabling inline view indexing
You can disable inline view indexing if you no longer want to use it. You can also temporarily disable inline view indexing to resolve a problem.