SQL Server

Written by Sam McGeown on 14/4/2011
Published under Microsoft
Configuring WSS or SharePoint Services for a small client is a pretty effective way of getting a document management solution for a reasonable cost point. One of the limitations that caused headaches was that it used to have a maximum storage of 4GB, which was the database limit. If you wanted to go larger, you would need either a) multiple SPS installations, b) a full version of SQL server, or c) the full version of MOSS.
Written by Sam McGeown on 1/4/2010
Published under Microsoft
If you install Reporting Services on Windows Server 2008 (RTM or R2) and attempt to verify the installation by opening the http://SERVER/ReportServer site, you may well see the following message: Reporting Services Error -------------------------------------------------------------------------------- The permissions granted to user ‘MCGEOWN\Sam.McGeown’ are insufficient for performing this operation. (rsAccessDenied) Get Online Help SQL Server Reporting Services Additionally, you may be able to access the http://SERVER/Reports site, but will have no permissions: You may also spend a good while checking DB permissions, IIS configurations, file permissions and so on.
Written by Sam McGeown on 27/1/2010
Published under Microsoft and VMware
Configuring the Virtual Environment and Virtual Machines Note – this configuration will work for ESXi 4 upwards due to the server 2008 MSCS requirement for persistent SCSI-3 reservations. The first step is to create a new vSwitch for the host-only cluster heartbeat network, don’t assign any network adaptors to the switch as it’s going to be local only. Create a new virtual machine with a single hard disk. For the purposes of this test, I’ve assigned 2 vProcessors, 1GB RAM, 30GB drive for the OS, 1 vNIC in the default vSwitch0.
Written by Sam McGeown on 9/10/2008
Published under Microsoft
32-bit processors have a limitation of only being able to directly address 4GB RAM - their architecture was never designed to address more. 64-bit processors get around that limitation by being able to us 64 bits to address RAM (potentially 16,777,216 GB), but what do you do if you have an application that won’t work on a 64-bit copy of Windows, but does need to utilise more than 4GB of RAM?