I’ve got a client who has a few users complaining that their disk thrashes when they take a new replica of a database, or there have been significant changes to it, even if they don’t open that replica.
I investigated this by taking a new replica myself, and found that some views (55 of a total of 133) were being auto-indexed in the background, even though I had not opened them.
I’ve looked at the view designs, as well as the view document items, and cannot find anything common just to those that are getting indexed. Also, this is the first time I’ve seen Notes index a view before it’s opened in some way.
All views are marked as “Refresh Auto, after first use”.
Anyone know what would cause some views to be indexed automatically ?
Subject: RE: What would cause some views to auto-index in a new replica ?
I think I’ve found the answer, and it came as a complete surprise.
What I’m observing is that when you create a replica, after the replication of the documents is complete, the backgound index program will build an index for every view that had an index on the server copy.
I’ve never seen this documented, and can’t see any reference in the help.
(The issue with the particular database I was investigating is that they have a lot of user-sort columns, and so the background index program was stressing their machine.)