I wanted to set up Microsoft Office SharePoint Server (MOSS) as a "mostly" single server install with the exception that I wanted to use the existing SQL Server 2005 installation instead of the embedded SQL Express Edition. To prepare for this, I added a second named instance to the SQL machine so that all MOSS traffic would be isolated and separately configurable.
The steps I took were to use Hyper-V manager to add a second processor and bump the allocated RAM up to 1 GB. After rebooting the VM, I went into Add/Remove Programs, selected the existing "Microsoft SQL Server 2005" entry and clicked "Change". On the "Microsoft SQL Server 2005 Maintenance" dialog, click the blue hyperlink above the list box for "To install a new component, click here". Browse for the install media and work your way through to the SQL database engine and choose it to add another one. Give this one a name (e.g. SQLMOSS) and continue through. When finished, be sure to use the Surface Area Configuration Tool to enable remote TCP/IP connections.
In my case, I decided to partition out the virtual as follows:
- 1/2 the memory (512 MB) maximum allocated to the SQLMOSS instance
- 1/2 of remainder (256 MB) for the development/play default instance
- other 1/2 of remainder left for the OS (Windows 2003 R2)
Here's a screen-shot of task manager running inside the Hyper-V remote console window:
Note that this was taken after configuration but before installing MOSS 2007.
The beauty of this virtualized approach is that I can add (or remove) processors and RAM depending on usage patterns and bottlenecks.