Menu
Capabilities: I had the recent pleasure of helping a client work through some very impactful performance issues with their on-premise CRM installation. These issues, which included SQL timeouts, excessive bandwidth consumption, outlook crashes and general slow performance, were causing poor user acceptance, lowered productivity, and negative impact on other business critical applications. We updated many database settings, tuned indexes, updated CRM registry settings and doubled the SQL Server RAM, but in the end the following 5 items provided the biggest performance boost to their Dynamics CRM instance. 1.) Reorganizing / Rebuilding SQL Indexes When you install Microsoft CRM, several System jobs are set up to keep your database running smoothly.
These routines include rebuilding fragmented indexes and cleaning up tables that contain data that is no longer needed. These jobs work great when your database is of moderate size, however if your database grows over 40 GB, these jobs may begin to fail.
![Microsoft crm 2011 state code and status code values meaning and examples examples Microsoft crm 2011 state code and status code values meaning and examples examples](/uploads/1/2/5/4/125499031/810942561.png)
![Microsoft crm 2011 state code and status code values meaning and examples examples Microsoft crm 2011 state code and status code values meaning and examples examples](/uploads/1/2/5/4/125499031/557510063.png)
There is so much information regarding the entity (id, Type, url, organization etc.) but not the state/status. I see 2 options: 1. Call the CRM WebService and get the information. Find the document element on the HTML and try to get it from there. Any one has better /simpler idea?
When this happens your database will begin to grow rapidly, and your indexes will quickly become fragmented. (My client had over 100 indexes fragmented at more than 80%, and a few tables that contained over 20 million unnecessary records.)These issues can lead to extremely slow performance and eventual SQL timeouts. Are You Experiencing These Symptoms? If so, you should turn off the out-of-the box index maintenance jobs and develop your own maintenance plan. You can get the tool from CodePlex to change the time that the maintenance plans run. (If you go this route, you’ll want to set the “Reindex All” and “Indexing Management” jobs to run sometime in the distant future, such as.) Once you have disabled these jobs, you will need to set up your own index maintenance jobs. I recommend using the SQL Server Maintenance Plan Wizard ( ).
Alternatively, you can create a SQL job to run the CRM 2011 index maintenance procedure pReindexAll, leaving the MaxRunTime variable null to ensure the job will complete.