
But as to exactly how long that load time is supposed to be, it hinges on a lot of factors, chiefly on extent of customizations and amount of data to be synched.Outlook works with gin and all email services. In theory this is supposed to help navigation later on and it´s supposed to take a bit longer at startup but offer a smoother navigation.īottom line: longer load times after first startup is to be expected. In case, for whatever reason the local DB has to be recreated, you can count on increased load time and reduced functionality while it is re-written.Īlso, after some changes in UR 15, the client also caches customizations, etc. Under normal circumstances, once the database is created, it´s only supposed to be updated and not completely recreated. Then a cyclical synchronization takes place (either/or automatic, manual).īecause this is how Microsoft programmed it, there is no way around the creation of the local databases.

Since the client does not have a ``real time`` link to the server, what it does is pull the data from the server into it´s local database and work witht he local data. They are needed for the client to function.

sdf files that are being created are the local SQL databases for the client. My question is, what is everyone else's experience when using the CRM Outlook client and if you have had performance issues was there any solution?Įnvironment: Citrix / Windows Server 2008R2 / Dynamics CRM 2011 UR18 / Office 2010 I have tried several solutions already ranging from modifying user and computer registry keys, enabling compression in IIS and pretty much anything I could find through searching forums. I haven't however found an example of at what point a deployment is "heavily customised". One thing to note is that reading the current documentation it states that heavily customised deployments will cause performance problems. We are now on Rollup 18 and performance has not increased. We contacted Microsoft when the issue first arose and were eventually told it would be resolved with subsequent rollups. We went from Outlook opening in less than a minute to it now taking 5-10min and then have the possibility for it hang again once users starting checking their main / looking at CRM data. Ever since updating from Rollup 10 (which caused a heap of other issues when it broke all of the old endpoints) we have continually had Outlook Performance issues when a user has the CRM Client enabled.
