This is an issue that is likely affecting thousands of Share Point users all over the world.
I am personally familiar with dozens of cases (if not more) where users were experiencing performance problems due to SQL contention that were resolved by performing a manual update of statistics.
I was recently approached by an old friend and MCS colleague (Greg Moss) who was working on a special project for a mutual customer.
This project was to conduct a health review of the database environment used to support a very large Share Point farm and came as a result of some unexplainable SQL performance problems that had hindered their environment for a few days.
The Share Point log indicates it ran an update every day even though we have verified that the date the statistics were last updated was over a month ago.
Furthermore, we learned that it not just a full database backup that can cause the operation to be skipped but also a differential and transaction log backup as well.
This is an issue that I have encountered in many environments and never dug deeper until Greg started asking questions.
This issue is an important issue and under investigation by the product development team.
What’s really troubling here, however, is that Share Point does not give any indication to the user that the statistics update operation was skipped.
In fact, as we saw in the Share Point logs above, it seems to lead one to believe that statistics were updated though they were in fact NOT updated.
An Access database is not a file in the same sense as a Microsoft Office Word 2007 document or a Microsoft Office Power Point 2007 slide deck.