Mittwoch, 1. August 2012
Dienstag, 31. Juli 2012
Default Performance Settings Dynamics CRM 2011
08:47
No comments
1. Limit the number of asynchronous jobs picked up for each organization
This topic has not yet been rated - Rate this topic Update Rollup 3 for Microsoft Dynamics CRM Server 2011 introduces a new deployment-wide setting that limits the number of asynchronous jobs that may be picked up for each organization. This setting may help reduce asynchronous operation backlog when multiple organizations are present. Without limiting the maximum number of jobs picked up, if a single organization in the deployment submits a large number of asynchronous jobs, such as 3,000 jobs, the Asynchronous Service may attend to those jobs first instead of attending to the fewer number of jobs submitted by other organizations. The following Windows PowerShell command sets the maximum number of items that can be queued to 100 for each organization in the deployment. Important You must apply Update Rollup 3 for Microsoft Dynamics CRM Server 2011 or a later version update rollup on all Microsoft Dynamics CRM server roles before you run this Windows PowerShell command.
To configure the number of asynchronous jobs picked up for each organization
Copy
add-pssnapin Microsoft.Crm.Powershell $itemSetting = new-object 'System.Collections.Generic.KeyValuePair[String,Object]'("AsyncSelectMaxItems",100) $configEntity = New-Object "Microsoft.Xrm.Sdk.Deployment.ConfigurationEntity" $configEntity.LogicalName="Deployment" $configEntity.Attributes = New-Object "Microsoft.Xrm.Sdk.Deployment.AttributeCollection" $configEntity.Attributes.Add($itemSetting) Set-CrmAdvancedSetting -Entity $configEntity
2.
This topic has not yet been rated - Rate this topic Update Rollup 3 for Microsoft Dynamics CRM Server 2011 introduces a new deployment-wide setting that limits the number of asynchronous jobs that may be picked up for each organization. This setting may help reduce asynchronous operation backlog when multiple organizations are present. Without limiting the maximum number of jobs picked up, if a single organization in the deployment submits a large number of asynchronous jobs, such as 3,000 jobs, the Asynchronous Service may attend to those jobs first instead of attending to the fewer number of jobs submitted by other organizations. The following Windows PowerShell command sets the maximum number of items that can be queued to 100 for each organization in the deployment. Important You must apply Update Rollup 3 for Microsoft Dynamics CRM Server 2011 or a later version update rollup on all Microsoft Dynamics CRM server roles before you run this Windows PowerShell command.
To configure the number of asynchronous jobs picked up for each organization
Copy
add-pssnapin Microsoft.Crm.Powershell $itemSetting = new-object 'System.Collections.Generic.KeyValuePair[String,Object]'("AsyncSelectMaxItems",100) $configEntity = New-Object "Microsoft.Xrm.Sdk.Deployment.ConfigurationEntity" $configEntity.LogicalName="Deployment" $configEntity.Attributes = New-Object "Microsoft.Xrm.Sdk.Deployment.AttributeCollection" $configEntity.Attributes.Add($itemSetting) Set-CrmAdvancedSetting -Entity $configEntity
2.
Sonntag, 22. Juli 2012
Dynamics CRM Web forms simplify the process of capturing visitors’ or users information from the website into your Dynamics CRM system. It is designed to automate importing of information from website into CRM and to enable non-technical users to design and publish their own web forms. The User or let´s say the Poweruser is enabled to create webforms on a User Interface and only copy and paste the background create code into the content Web Management System like Wordpress, Blogspot, Typo3 or any other Web Content Management System or Custom Website.
03:53
No comments
Abonnieren
Kommentare (Atom)










