Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
SQL Timeouts and Warnings RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi All,

    We were getting the below warning in one of our PROD environment.

    Query execution time of 30.0 seconds exceeded the threshold of 10 seconds. Thread: 28; Database: PROD_MSCRM; Server:PRODDB01; Query: update tablename set col=......

    Using below option, we have changed LongQueryThersholdInSeconds column value in ServerSetingProperties table of MSCRM_Config.

    update MSCRM_CONFIG..ServerSettingsProperties set IntColumn = '30' where ColumnName='LongQueryThresholdInSeconds'

    But how do i get CRM to recognize it? The error i’m getting still says what the original setting was. Not the increased time i set it to.

    Please advise me on this issue.

    Wednesday, April 13, 2016 11:04 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    If you're having SQL calls that take 30 seconds you'll need to have a look at the server what is happening and why it's taking that long. Can you recreate the issue and try to isolate what sort of call from CRM that is making this issue?

    Regards

    Rickard Norström Developer CRM-Konsulterna
    http://www.crmkonsulterna.se
    Swedish Dynamics CRM Forum: http://www.crmforum.se
    My Blog: http://rickardnorstrom.blogspot.se

    Thursday, April 14, 2016 7:27 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks Rickard for the response.

    Currently we are in the process of finding root cause of the issue.

    Btw, can you please tell me how CRM will recognize newly configured "IntColumn=30"? after executing above update statement do we need to reset IIS or server reboot is required?

    The error i’m getting still says what the original setting was. Not the increased time i set it to.

    Friday, April 15, 2016 5:54 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    You might need an IISReset, but you really shouldn't have to (don't know if these things are cached though). Anyway, if the SQL calls start taking 10-30s you will have angry users :)

    (no I haven't fiddled with these settings since when I've had issues with long SQL answers I've tried to address the issue rather than turning up the timeout. The other thing is that it's a warning and not an error.)

    Regards

    Rickard Norström Developer CRM-Konsulterna
    http://www.crmkonsulterna.se
    Swedish Dynamics CRM Forum: http://www.crmforum.se
    My Blog: http://rickardnorstrom.blogspot.se

    Friday, April 15, 2016 7:29 AM