Last post Mar 17, 2016 01:29 PM by PatriceSc
Mar 17, 2016 08:55 AM|itsathere|LINK
I had same problem few days ago and I have resolved it by below sql command
Is is good suggestion to resolve error or have another solutions
Mar 17, 2016 01:07 PM|Weibo Zhang|LINK
About using the “exec sp_updatestats”, I suggest you’d better first have a look at below links to learn the consequences of it. As it says, it’s the least recommendable option. So, you’d better use it carefully.
As I searched, I think you could refer to below links to find out the real issue points step by step and then solved them instead of directly running “exec sp_updatestats”.
Mar 17, 2016 01:29 PM|PatriceSc|LINK
The point would be first to fully understand the error (ie full call stack and maybe the offending line of code). For now it would look like some kind of locking timeout maybe? You perhaps indirectly fixed that by updating the stats though the db should
have taken care of that (unless maybe if you just have done massive imports to the db).
The point anyway would be first to fully understand the intial error you had and its cause before seeing if what you have done was really the way to fix that...