locked
CRM Hangs on LocalizedLabel query RRS feed

  • Question

  • Hey everyone,

    Recently we've been experiencing an issue in CRM where a certain query hangs the entirety of the organization until it finishes running.  This particular query doesn't look like it's something that would force the organization to hang like it does, but we saw it in our DEV environment and now see it in PROD.

    Here's the query:

    select VersionNumber, CONVERT(bigint, VersionNumber) as VersionValue from LocalizedLabelView order by LocalizedLabelId

    So I'm fairly certain this query fires whenever an object (not record) is saved within the organization; please let me know if that's not the case (we're trying to track down the action that causes it).  We added an index to LocalizedLabelId this morning and are hoping that helps eliminate these hangups.

    Has anyone else experienced this issue?

    Tuesday, December 15, 2015 3:08 PM

Answers

  • We may have fixed the issue.

    The indexing on the table in question was pretty weak, serving really only the most basic of needs within CRM.  If you reach a point of customization where CRM is more your company than it is CRM, you're going to need to add a few indexes to that table to support the massive save and publish operations run against it.  That's what our issue was.  We've been using and customizing CRM for well over three years now and it's more us than it is CRM anymore.  Our save and publish operations were taking an outrageous amount of time to complete and adding a few indexes not only reduced those times, but it seems to have eliminated the timeouts and hangs when that table was scanned.

    • Marked as answer by Josh Waclawski Monday, December 28, 2015 5:54 PM
    Monday, December 28, 2015 5:54 PM

All replies

  • I have not seen this issue in all the years I've been working with CRM.  This looks like it is related to customization or a third party solution but I could be wrong. Where did you find the query?  At a minimum it should have a nolock.

    Regards, Donna

    Monday, December 28, 2015 5:14 PM
  • We may have fixed the issue.

    The indexing on the table in question was pretty weak, serving really only the most basic of needs within CRM.  If you reach a point of customization where CRM is more your company than it is CRM, you're going to need to add a few indexes to that table to support the massive save and publish operations run against it.  That's what our issue was.  We've been using and customizing CRM for well over three years now and it's more us than it is CRM anymore.  Our save and publish operations were taking an outrageous amount of time to complete and adding a few indexes not only reduced those times, but it seems to have eliminated the timeouts and hangs when that table was scanned.

    • Marked as answer by Josh Waclawski Monday, December 28, 2015 5:54 PM
    Monday, December 28, 2015 5:54 PM