I have recently moved my DB over to a full version of SQL server 2008 R2.
As standard practice on this DB server, all DB's are backed up and maintenance conducted for optimisation etc, this includes a periodic reindexing.
However since I moved VeeamOne database over to the SQL server, the indexing operation has failed due to 4 indexes in VeeamOne having page level locking disabled.
The reindexing problem can be fixed by enabling page level locking, however I am concerned that this setting may have been deliberate, as it is very unusual to find this disabled in any database.
I can only suspect that maybe Veeam is aware of a deadlock possibility with this enabled??? I cannot think of any other good reason this would be done? Sometimes it is unintentional, however I would like to check if it is appropriate to enable page level locking so this DB can be included in my maintenance plan, or should these settings be kept disabled?