Like a c lock, but distributed so its a lock that can be used by all active processes. We use distributed locks to synchronize access to resources. The above simply means the transaction has reached the innodblockwaittimeout while waiting to obtain an exclusive lock which defaults to 50 seconds. Just some info: when you see Lock request time out period exceeded this isnt an SQL connection timeout or load balancing problem, or a SQL problem.
#LOCK REQUEST TIME OUT PERIOD EXCEEDED WINDOWS#
Also, we changed the new maintenance windows of the database to only on weekend days but the errors are still happening during week days.ĭoes anyone know what could be causing this sudden problem? Has Microsoft changed anything to databases and/or data factories that we are not aware of? What could we do to try and prevent these errors? We are kind of at a loss here. One of the most popular InnoDB’s errors is InnoDB lock wait timeout exceeded, for example: SQLSTATEHY000: General error: 1205 Lock wait timeout exceeded try restarting transaction. We have tried rescaling the SQL database to simulate a restart (since Azure SQL Databases can't be restarted.) but that has not helped. Note the SPID of this query window connection. In the lower right hand corner of SSMS, you should see the username and (in parentheses) the SPID of the connection youre using.
Also, the errors seem to be happening at random and are not tied to any specific pipelines or data flows. Lock request time out period exceeded / 1LT/INS trigger creation failed for table