Rambles of Ev

http://www.sqlteam.com/article/sql-server-2000-performance-tuning-tools

http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/rdbmspft.mspx#EZPAC

Hopefully most people know that MOSS is a superset of WSS. In other words, MOSS takes the foundation laid by WSS v3.0 and expands upon it, creating features that sit on top of it, utilize the core WSS framework, and extend it in such a way that is beneficial to larger companies, enterprise deployments, and portal scenarios. The following is a list of things that MOSS provides that WSS v3.0 does not. I figured it would be a waste of text to show the features that the two have in common, or the places in which MOSS re-uses WSS functionality without change or enhancement.

http://dotnetaddict.dotnetdevelopersjournal.com/moss_vs_wss.htm

http://office.microsoft.com/en-us/sharepointtechnology/FX101758691033.aspx?ofcresset=1

http://blogs.officezealot.com/rbedell/archive/2005/10/27/8365.aspx

http://support.microsoft.com/?kbid=331062

http://www.jeremyroe.net/?p=20

Tonight while doing maintenance on one of my virtual machines I decided it was time to remove a snapshot I created a few days ago while upgrading some software. Shortly after hitting the “remove snapshot” selection my vmware console crashed with a lost pipe error.

Attempting to reconnect yeilded:

There was a problem connecting:
511 Error connecting to /usr/bin/vmware-serverd process

I was almost ready to reboot the machine when painful memories of my last vmware snapshot gone bad experience entered my mind. I investigated further and found that there were .WRITELOCK files in place in my virtual machine folder. After checking my processes on my vmware box I noticed a file called “sdhelper” using a bit of cpu time.

After a brief google search I stumbled across this article which stated that in the event of removing large snapshots it is not unusual for the console to loose connectivity. It is important to simply wait it out and it will eventually finish recombining your disks and restore your connectivity.

I know from prior experience that snapshots are very finicky creatures and rebooting your machine at a time like this could easily lead to data corruption and the loss of your virtual machine.