Help get this topic noticed by sharing it on Twitter, Facebook, or email.

Calling SP_Refresh concurrently on the same object

I believe it's not desirable to call SP_Refresh concurrently on the same object. What's the best way to prevent this? We have a SQL job that runs periodically to refresh local tables. But, our application also could be calling SP_Refresh on the same object(s) to trigger some business process. How to prevent the two from executing at the same time.

If a row lock is placed on TableRefreshTime table when SP_Refresh is called, then I believe the problem is solved. However, I don't see it anywhere in the documentation.
1 person has
this question
+1
Reply