Attached is the powerpoint I received. I have asked Rob for the docs referenced in slide 57.
The issue I found at a customer install was that Tomcat 6 doesn't like SQL Server instance names; it only wants the server name and the port. If you only have the default instance, no problem. However, this customer had a default instance belonging to their Crackberries and so I installed SQLExpress for them to try out CRM with.
[Warning: bring your HHGTTG cover and a towel with you for this]
First, in SQLExpress, make sure SQL is using a fixed port, not a dynamic one. Restart the service for the port change to take effect.
Then in Sage CRM, go to the admin | System | Database page, and take the instance name off of the Default Database Server field. When you click Save, you should see a message that the new db info will be passed to Tomcat. You will then see ""You may need to recreate views manually"" and a ""log on again"" button in CRM.
Don't Panic!
(that's for those who did not get the reference in the original warning)
Open up regedit, navigate to [HKEY_LOCAL_MACHINE\SOFTWARE\eWare\Config\/CRM] (the characters between Config and CRM are the two different slashes, not a V) and edit DefaultDatabaseServer to put back the instance name. Run iisreset and Sage CRM and Tomcat will now have the database info the way they each want it.