none
WSS Limitations - What should my client know?

    Question

  •  

    Dear SharePoint Team;

     

    I am planning to push for WSS for a client project but I would like to know more about WSS' limitations, especially database size:

     

    Can you please confirm that there is no database size limit if we use SQL 2005 Standard, right? If we use SQL 2005 Express then we are limited with 4GB and this is actually not a WSS limitation, am I right?

     

    What are the top 5 limitations of WSS, please? Can you comment.

     

    Thank you team...

     

     

    Wednesday, December 05, 2007 1:57 AM

Answers

  • With WSS you have three options for the backend database provider for your Config and Content databases:

    • Windows Internal Database - as I understand it, you have no size limitations when you install using the Windows Internal Database option (it installs seamlessly with WSS if you choose to use it), but you can only administrate it via the command line and it has to be on the same server as your WSS install, so you lose a lot of flexibility with its use.
    • SQL Server Express - With SQL Server 2005 Express (or its predecessor the MSDE), you can set up your database remotely or on your WSS server, but you face limitations (4 GB database size with 2005, 2 GB and performance throttling w/ MSDE).  You can administrate it using a GUI tool, and you can't beat the price, but you will quickly come up against the 4 GB limits.
    • SQL Server 2005.  No database limits, GUI admin tool, remote capabilities.  The only limits on your database size are your available disk space and how your DBAs feel about large DBs.  Large DBs take much longer to recover from backups, which is one reason why people like to stay away from them.  But SharePoint (WSS or MOSS) does not have any sizing constraints on database sizing.

    From a configuration perspective, the database decision is really the only one that should impact the architecture of your WSS farm.  You can configure multiple load-balanced front end servers pointing to a back-end database, and that database can be clustered if you desire.

     

    From a limitations perspective, there are several features that you get with MOSS 2007 that aren't available in WSS...

    • Search and cohesion across site collections - In WSS, each site collection is an island unto itself.  MOSS adds the portal umbrella that pulls together those separate site collections and allows for searching across them
    • Personalization - MOSS allows users to have individual, personalized MySites; WSS doesn't.
    • User Profiles - MOSS allows you to import, store, and update personal data on your users, its not available in WSS
    • Audience Targeting - MOSS allows you to target content to specific user groups; WSS doesn't.
    • Crawl and Index sources outside of SharePoint - MOSS allows you to return search results for indexed sources such as file shares, web sites, Lotus Notes databases, and much more; WSS can only crawl and index SharePoint sites.
    • Search administration and customization - MOSS gives its admins much more control over the configuration of its search engine; WSS doesn't.
    • Site Templates - MOSS provides additional site templates (and workflows) for content management and portals; WSS does not have these templates

    For more information on the differences between WSS and MOSS, you might want to check out the following links:

    Microsoft site detail features available across SharePoint product SKUs:  http://office.microsoft.com/en-us/products/FX101758691033.aspx

    A blog post I wrote comparing WSS and MOSS functionality and intended uses: http://office.microsoft.com/en-us/products/FX101758691033.aspx

     

    EDIT: Just found this link for limitations of MOSS with regards to the number of sites you can have in a collection, etc.

    http://www.bobmixon.com/blog/Lists/Posts/ViewPost.aspx?ID=31

    Wednesday, December 05, 2007 3:13 PM

All replies

  • The size of content DB is certainly not a limitation due to WSS 3.0.  It depends on the flavor of SQL Server (Express/Standard/Edition). I've seen enterprise customers having content DB more than 80GB with WSS 3.0.

     

    It does not sound correct for me to compare WSS 3.0 and MOSS 2007 and come up with a limitation about WSS 3.0. WSS 3.0 is the base-platform. MOSS 2007 is built on top of WSS 3.0.

     

    Anyhow, please look at the following WSS 3.0 FAQ by Mike Walsh

    http://wss.collutions.com/pages/WSS%20v3%20FAQ.aspx

    This would give you some good insight about what you are looking for

     

     

     

     

     

    Wednesday, December 05, 2007 6:02 AM
  • With WSS you have three options for the backend database provider for your Config and Content databases:

    • Windows Internal Database - as I understand it, you have no size limitations when you install using the Windows Internal Database option (it installs seamlessly with WSS if you choose to use it), but you can only administrate it via the command line and it has to be on the same server as your WSS install, so you lose a lot of flexibility with its use.
    • SQL Server Express - With SQL Server 2005 Express (or its predecessor the MSDE), you can set up your database remotely or on your WSS server, but you face limitations (4 GB database size with 2005, 2 GB and performance throttling w/ MSDE).  You can administrate it using a GUI tool, and you can't beat the price, but you will quickly come up against the 4 GB limits.
    • SQL Server 2005.  No database limits, GUI admin tool, remote capabilities.  The only limits on your database size are your available disk space and how your DBAs feel about large DBs.  Large DBs take much longer to recover from backups, which is one reason why people like to stay away from them.  But SharePoint (WSS or MOSS) does not have any sizing constraints on database sizing.

    From a configuration perspective, the database decision is really the only one that should impact the architecture of your WSS farm.  You can configure multiple load-balanced front end servers pointing to a back-end database, and that database can be clustered if you desire.

     

    From a limitations perspective, there are several features that you get with MOSS 2007 that aren't available in WSS...

    • Search and cohesion across site collections - In WSS, each site collection is an island unto itself.  MOSS adds the portal umbrella that pulls together those separate site collections and allows for searching across them
    • Personalization - MOSS allows users to have individual, personalized MySites; WSS doesn't.
    • User Profiles - MOSS allows you to import, store, and update personal data on your users, its not available in WSS
    • Audience Targeting - MOSS allows you to target content to specific user groups; WSS doesn't.
    • Crawl and Index sources outside of SharePoint - MOSS allows you to return search results for indexed sources such as file shares, web sites, Lotus Notes databases, and much more; WSS can only crawl and index SharePoint sites.
    • Search administration and customization - MOSS gives its admins much more control over the configuration of its search engine; WSS doesn't.
    • Site Templates - MOSS provides additional site templates (and workflows) for content management and portals; WSS does not have these templates

    For more information on the differences between WSS and MOSS, you might want to check out the following links:

    Microsoft site detail features available across SharePoint product SKUs:  http://office.microsoft.com/en-us/products/FX101758691033.aspx

    A blog post I wrote comparing WSS and MOSS functionality and intended uses: http://office.microsoft.com/en-us/products/FX101758691033.aspx

     

    EDIT: Just found this link for limitations of MOSS with regards to the number of sites you can have in a collection, etc.

    http://www.bobmixon.com/blog/Lists/Posts/ViewPost.aspx?ID=31

    Wednesday, December 05, 2007 3:13 PM
  • Thank you all for your responses. It helps a great deal. Happy holidays

     

    Wednesday, December 05, 2007 5:38 PM
  • Thank you all for your responses. It helps a great deal. Happy holidays

     


    Friday, July 16, 2010 3:33 PM
  • Thank you all for your responses. It helps a great deal. Happy holidays

     



    Hii ,

    As well the same query am having which we are trying to push Sharepoint foundation/WSS 4.0 to one of my client whether is there any limitations for Sharepoint foundation Database constraints while am gonna take a challenging project is that it's a Document management and also looking to host it on cloud !!!!!!!!!

    Thanks in advance......
    Friday, July 16, 2010 3:41 PM
  • All the links mentioned in this post are obsolete.
    Tuesday, November 05, 2013 11:03 AM