0

We have configured transactional replication. Today for some reason replication started to lock users running reports. By running sp_who2 I saw that replication job is constantly doing update and locking users. After several hours I restarted agent job, but locks have not ended. So, I have found the table that were causing locks and removed them from replication and added back. But it also have not solved the issue. There are no errors in replication monitor. Is there a way to solve this issue? And how do I restore only the data that was rolled after server restart?

  • You'll love sp_WhoIsActive for things like this, and will replace sp_who2 completely. I'm not sure why you think the table locks would stop as long as updates were happening and whatever level of lock is required were being acquired. Restarting the job wouldn't change that. This question may be what you are looking for – scsimon Jun 21 at 20:59

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.