Now that we have been able to work first hand with SharePoint Foundation 2010, we are beginning to _really_ like it.
- Learning curve is minimal due to already being used to using the Office Ribbon.
- Task placement on the ribbon is very intuitive.
- Site creation and management is a lot more intuitive.
We have begun to customize our in-house SharePoint Foundation 2010 Companyweb site around the way we have been wanting to work with SharePoint since version 3’s introduction.
Timing was such that we did not have any available to set up a separate server for a WSS v3 configuration. So, we stuck it out with a combination of file shares, SharePoint v2 on our SBS, and SharePoint v3 (our WWW) hosted by OWN.
Our current SBS 2003 R2 server which is now officially out of the SBS role was way too tired to take on the task of running SharePoint v2 and v3 side-by-side.
Given the fact that we will be using our Companyweb to store virtually all of our live documentation, archives, and more we have moved the SharePoint Foundation 2010 content database onto a dedicated SQL 2008 x64 server.
We did start working with the new Companyweb before the content databases were moved over to SQL so we saw a significant improvement in the Companyweb site’s performance after the move.
For those clients where SharePoint will be used a lot, a separate SQL server configuration would be an important performance consideration.
Have a great weekend and thanks for reading! :)
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book