Can anyoneĭetermine how to fix this issue? It doesn't happen with other triggers, justĪlter failed for Trigger 'TRG_MyTriggerName'.Īn exception occurred while executing a Transact-SQL statement or batch. Trigger and select 'disable' I receive the error pasted below. If the transaction is still holding the lock, terminate that transaction if appropriate. The information given is quite vague, and I am not at all acquainted with Tomcat-8. I have changed the Table and Database Designers transaction timeout after to 30000 sec as suggested by some of the Forms. Yes if you have Standard edition ONLINE index rebuild is not possible and you have to make sure application or some query is not accessing the table otherwise index rebuild would fail. 'LOCK request timeout period exceeded.' But the same trigger has been ALTER/DROP in other database containing same table. By default, there is no lock timeout in SQL Server, but it is possible that Object Explorer in SSMS sets one up, so it will remain unresponsive forever if there is blocking. Please note in any case you dont have to take SQL server database or SQL Server instance offline to rebuild any index. I've tried disabling a trigger via SSMS (VS2005) query window and it takesįorever 'executing', until I just cancel it. I don't think there is a way to configure that lock timeout of 10 seconds.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |