In my company we are 5 developers who work on same organisation.
We used a single server with SQL and Dynamics CRM installed.
If two developers publish customizations at the same time, we need to restart IIS.
Do you have any suggestions to optimize SQL Server or IIS to avoid this issue?
On
If you are developing webresources, you can use this little hack webresource proxy as workaround. Basically, it just replaces the content of the webresource by the response of generic web server. You don't need to update and publish webresource anymore.
Currently in the way CRM works, publishing will slow everything down and potentially lock the SQL server up.
Your options would to be to only publish when necessary, so you minimize your disruption to your developers. For stuff like form design, I would recommend not publishing, but, to preview the from to see your new changes.
Upgrading your servers with more memory and so on will help reduce the time taken to publish. Sorry this is not much help.