Nicknow is correct in that you have to get some metrics and figure out if this is truly a client side CRM Outlook performance issue or if it's a server side issue that may be due to poor SQL Server or poor Microsoft CRM Server performance. Once I could narrow down the specific performance and I had a control organization - running in the same environment - to use for comparison I would go to Serverfault and post a specific question with all the relevant details (custom entities, workflows/plugins, server config, sql configuration/indexing, workstation setup, network topology, etc.) for each performance issue you are experiencing. This is where I would start if I knew absolutely nothing about the system and its history. What is the performance difference? Can you account for this performance difference because of plugins executing? Perform updates, assigns, deletes, etc and make the same measurements. Create a new organization in CRM and create some accounts and contacts during a period of low-load in both the new organization and the current organization. Now, once you have the specific performance problems you need to determine if CRM - at a baseline in your environment - is performing acceptably. Otherwise, you'll never know where to look and you won't know if you have fixed it. There is a big difference between the problem of "when I first launch CRM it takes 30 seconds to load" and "when I save a new Account record it takes 25 seconds" - you must get the problem statements down to these types of specifics.
You first need to define the specific metrics for "slow" - must be repeatably measurable, not just a user's opinion. On Weekly basis, end users complain that the CRM is running slow on
0 kommentar(er)
