In Sitecore databases, the EventQueue table contains both local and remote events of Sitecore instances.

Why is there a need to track local events? Can't they just be handled internally in the instance that fired them?


Yes many types of events can be handled locally, not required to be shared to other servers.

See solution #2 at https://kb.sitecore.net/articles/930920 -- using the FileBasedPropertyStore has reduced volume of the EventQueue by 60% or more for some of the large implementations I've worked with. It shifts the specific events to the file system of IIS instead of SQL Server.

  • Why do these events need to be stored somewhere, at all? Can't they be kept in memory? Oct 5 '16 at 18:47
  • I can't speak for "all" the events since I'm not certain what they all do, but mostly the local-only ones I've seen are for data like timestamps for when an index was last modified etc. I would think persisting that beyond app pool recycles would be important, but maybe not in all cases.
    – G Killian
    Oct 5 '16 at 18:50

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.