New answers tagged

0

I had a similar issue some time ago, I resolve it by disabling the lock escalation. use tempdb create table my_test( ind int not null, book varchar(50) not null, constraint pkmy_test primary key clustered (ind)) select * from sys.tables where name ='my_test' ALTER TABLE dbo.my_test SET (LOCK_ESCALATION=DISABLE) ALTER TABLE dbo.my_test REBUILD ...


0

In my experience, Sql Server sometimes wants to scan small tables (even when they have indexes that you'd think would be used) which can lead to deadlocks on a hot table. It might be a kludge solution, but I've had tables like this and was able to solve my problem by actually adding lots of 'bogus' rows to 'widen' the table and force Sql Server (optimizer)...


0

So I didn't got any luck with the deadlock graph. Doesn't seem to appear in my SQL Logs. But, I did find out that another job has been scheduled to run at the same time than my job, and it was taking backups and sending e-mails at the same time that my job was trying to cleanup the mail history. So changing the schedule of the other job got my problem solved!...


0

http://dev.mysql.com/doc/refman/5.6/en/innodb-autocommit-commit-rollback.html If a session that has autocommit disabled ends without explicitly committing the final transaction, MySQL rolls back that transaction. There is a process that monitors active sessions. If any are found to have disconnected, the sessions are cleaned up. This includes rollback ...


1

This error is produced for various reasons stated below: Too high activity - Re-running the job during a less busy period can fix this ORA-00060 deadlock error. Poor application design - As noted in the trace file: "The following deadlock is not an ORACLE error. It is a deadlock due to user error in the design of an application or from issuing ...


2

Sybase ASE uses blocking locks for transaction isolation, meaning that readers block writers and writers block readers (unlike other databases which use versioning so that writers don't block readers and vice versa). So each SELECT is blocked by the exclusive lock taken out by the earlier UPDATE on the table it is selecting from, since that update was done ...


1

System Center Operations Manager (SCOM) with the SQL Server Management Pack can alert on deadlocks if you enable logging for message 1205. You can enable it with the following SQL query: EXEC sp_altermessage 1205, 'WITH_LOG', 'true'. Also, see my answer to "Why isn't the objectname and indexname populated in deadlock graph?" for a PowerShell script I wrote ...



Top 50 recent answers are included