Timeout when using the Commit Changes Tab

Lewiethegreat · January 15, 2014 12:41AM

When ever I try to commit my work I get Timeouts on the Commit Changes tab. I never even get to see what to commit and the error appears before this occurs. I am able to use SQL Compare 10 without any timeout issues.

Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Lock request time out period exceeded.

James B · January 17, 2014 5:35AM

Hi,
Sorry to hear you're running into this. If it's suddenly started happening then it's possible that one user has a stuck lock on our change-tracking table. The quickest way to fix that is to usually get everyone to restart SSMS, although in some rare cases it seems to require the SQL instance to be restarted instead.

If you've actually been experiencing the problem more and more frequently over time, it may indicate a different issue happening though, so let us know if that's the case.

Lewiethegreat · January 19, 2014 4:41PM

To resolve it I I did a sp_who2 and determined which locks where occuring. I then killed the locks and the problem has gone away. The locks where on tempdb.

James B · January 20, 2014 6:54AM

Yep, that'll do it too.
To stop it using tempdb, you can force it to use a database you create specifically for the purpose: http://documentation.red-gate.com/display/SOC3/Logging+changes+to+shared+databases#

Timeout when using the Commit Changes Tab

Comments

Product Learning

Community Forums

Events & Friends

Simple Talk