You should check the QueryLog which transactions were running in parallel.
Collect Stats is first using an Access lock and after the collection it's merging the new info, but i would rather expect a "3603 Concurrent change conflict on table".
Do you get this error every time or randomly?
Dieter
You should check the QueryLog which transactions were running in parallel.
Collect Stats is first using an Access lock and after the collection it's merging the new info, but i would rather expect a "3603 Concurrent change conflict on table".
Do you get this error every time or randomly?
Dieter