![]() ![]() The deadlocks are caused by SQL queries/stored procedures processing the large number of recipients and their corresponding large number of display name and email address entries in a certain Analytics SQL table where the SQL table does not have indexes on the columns being queried. Reference: EVSqlCommand: DB: Data Source= Initial Catalog= Integrated Security=True Connect Timeout=3600 - Command: usp_StoreDiscoveredItemDetails_update_insert Rerun the transaction.Ī database error was resolved after Xms and X retries.Įrror: Error Code: 1205 / X - Severity 13 - Transaction (Process ID X) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. ![]() Last Error: Transaction (Process ID X) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Enterprise Vault will try to run the command again.Ĭommand: 'EVSqlCommand: DB: Data Source= Initial Catalog= Integrated Security=True Connect Timeout=3600 - Command: usp_StoreDiscoveredItemDetails_update_insert' The Information Events as listed below may be seen in the EV Event Logs on the DA server.Ī transient error is preventing the execution of a SQL command. When a large number of such messages is processed, the number and/or frequency of SQL deadlocks could increase and could potentially pause or stop Analytics processing. When such messages are processed by DA Analytics, the Analytics background processing of these messages may result in SQL deadlocks. These messages can be Archived by Enterprise Vault (EV) SMTP Archiving and can be found by Discovery Accelerator (DA) Searches. Bloomberg messages can contain hundreds of recipients, with some numbering into the thousands.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |