Archive for the ‘SharePoint’ Category

Difference between WSS and MOSS

Friday, April 24th, 2009

When we describe SharePoint to our customers, we often need to describe the difference between WSS and MOSS.  Here are the highlights.

SharePoint = WSS 3.0 or MOSS 2007 (or both)

WSS = Windows SharePoint Services 3.0
MOSS = Microsoft SharePoint Server 2007

The previous version of SharePoint was WSS 2.0 + SPS 2003 (SharePoint Portal Server), but we will be talking about WSS 3 and MOSS 2007 here.

WSS is part of Windows Server, specifically Windows Server 2003 and Windows Server 2008.  It is not automatically installed.  You must first install IIS (Internet Information Server) and ASP.NET 2.0, plus .NET 3.0.  These components are found either on your Windows Server media (CD/DVD) or through Windows Update.  The important thing to understand is WSS is part of your Windows Server license.

MOSS is a separate product.  MOSS requires either a MOSS Standard or MOSS Enterprise license.  These both install from the same media, just require a different activation key.  MOSS builds on top of WSS and adds additional components such as enhanced search, My Sites, Business Data Connector, Excel Services, and other features.

WSS and MOSS offer many of the same collaboration features:

  • Site provisioning
  • Document management (check in/check out)
  • Discussions
  • Wikis, Blogs, RSS Feeds
  • Basic workflow
  • Custom lists

MOSS builds upon WSS and adds:

  • Additional workflows
  • Web content management (web publishing features)
  • Records management
  • Auditing
  • Additional search such as people search
  • My Sites (each user has their own personal site with public and private areas)
  • Enterprise features such as Excel Services and BDC

Both WSS and MOSS use SQL Server to store content and configuration.  If you don’t explicitly install or configure SharePoint to use a specific SQL Server instance, the stand alone installation will create something called Windows Internal Database (which is a variant of SQL Server Express).  This special version of SQL Server should be avoided for most business installations of SharePoint.  But you can use Windows Internal Database for development, demo, or trial instances of SharePoint.

For more information about the differences here are some more descriptions:

SharePoint Saturday Boston on March 14, 2008

Tuesday, January 27th, 2009

ThirdM will be one of the sponsors at SharePoint Saturday Boston on March 14, 2008.  Talbott Crowell will be speaking at the event as well.  If you are interested in attending or speaking check out http://www.sharepointsaturday.org/boston.

Automating SQL Server Database Creation for SharePoint

Friday, January 23rd, 2009
Talbott Crowell will be speaking tomorrow at New England Data Camp 1.0 tomorrow on. Here is the synopsis:
Automating SQL Server Database Creation for SharePoint
In this session, Talbott will discuss the use of the SharePoint API for provisioning content databases in SQL Server to store documents. There are several scenarios that you will want to control and manage the database creation when building specialized applications using SharePoint. Topics include planning and estimating size requirements plus strategies around partitioning data into content databases. Attendees include SQL Server DBA’s supporting SharePoint installations and applications.
When: Saturday, January 24 at 11:15 AM to 12:30 PM
Where: Microsoft Waltham Office, 201 Jones Road, 6th Floor, Waltham, MA
Register: Click to attend

ThirdM at SharePoint Saturday New York

Sunday, December 14th, 2008

Talbott Crowell, ThirdM’s Chief Software Architect, will be speaking at SharePoint Saturday, New York, on Feb 21, 2009 at the Microsoft office in New York City.

Watch for updates.