mssql_v2005
asked on
SQL Timeouts and Warnings+CRM 2011
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 LongQueryThersholdInSecond
update MSCRM_CONFIG..ServerSettin
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.
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 LongQueryThersholdInSecond
update MSCRM_CONFIG..ServerSettin
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.
Feridun Kadir
I would have thought an IISRESET or server reboot should get the new setting recognized.
Hi,
If that also does not do the thing for you, you need to consider following findings:
1. Observe the operation when this error occurs.
2. Observe the query which is getting fired when this error occurs and do some research on it. Find the columns which requires indexes on it.
3. If there are any SDK calls for this operation to fetch records from CRM, try to use FetchXml and QueryExpression with "NO LOCK" property specified with it.
If that also does not do the thing for you, you need to consider following findings:
1. Observe the operation when this error occurs.
2. Observe the query which is getting fired when this error occurs and do some research on it. Find the columns which requires indexes on it.
3. If there are any SDK calls for this operation to fetch records from CRM, try to use FetchXml and QueryExpression with "NO LOCK" property specified with it.
ASKER
@Rikin Shah: We have already executed point 2 & 3. Still we are getting same warning message.
@Feridin: We have configured IIS in different server. Do we need to reboot IIS server and DB01(PROD DB server) as well?
@Feridin: We have configured IIS in different server. Do we need to reboot IIS server and DB01(PROD DB server) as well?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Sounds like table locking issue .
Login to your SQL server and take a look at the activity monitor. The overview window should show you which process is in LOCK state. You can remove the locked process and it should work.
Login to your SQL server and take a look at the activity monitor. The overview window should show you which process is in LOCK state. You can remove the locked process and it should work.
ASKER
Thanks Lucas911. We will check and will update you if we found any locking issues.
Hi Feridun,
We have to explain this situation (above warning) to our customer in detail like symptom, rootcause and resolution. I am not able to find any MSDN/Microsoft link related to above warning. Can you please share MSDN link for this.
Thanks in advance.
Hi Feridun,
We have to explain this situation (above warning) to our customer in detail like symptom, rootcause and resolution. I am not able to find any MSDN/Microsoft link related to above warning. Can you please share MSDN link for this.
Thanks in advance.
I'm not sure that cahnging the warning threshold is documented in MSDN but there are a lot of posts on this topic by many people.
ASKER
--