More reasons to ensure you’re not exceeding capacity planning guidelines


If I don't harp on it enough 🙂 I knew I had seen the official KB on this subject long ago, and finally came across it again.


http://support.microsoft.com/default.aspx?scid=kb;EN-US;830601


Keep in mind, that even with a MOSS 2007 indexer, indexing SharePoint Portal Server 2003 and Windows SharePoint Services 2.0 sites, this is going to cause the same impact, as the impact/delay comes from the target system.  It's not that the indexer is performing badly...It's just that it's waiting on the target to satisfy the data request.


How bad could you possibly be impacted by this?  Run SPSiteManager in a level 3 analysis, then look at the various <warning> elements that inform you where you have document libraries, and lists that have exceeded our capacity planning guidelines for Windows SharePoint Services 2.0 and SharePoint Portal Server 2003.


 - Keith


 



More information:


Comments (4)
  1. tony roth says:

    no updates since 2004 on this?

  2. krichie says:

    This was based on the RTM release of SharePoint Portal Server 2003 and Windows SharePoint Services 2.0.  These were the capacity planning limits imposed at the release of that product.   No architectual changes were made to the underlying system that would mitigate changes to these limits.

    In V3, we’re still waiting on the official released limits, so that’s when you’ll see the updates for this.

  3. Trevor Williamson says:

    I’m looking for the new stats on MOSS 2007 as well…I guess I keep looking.

    (BTW, nice blog Keith, great info source!)

  4. krichie says:

    It’s something I’m eagerly awaiting myself 🙂 Once i find out it’s public, I’ll definately link to it here.

    Thanks for the blog plug Trevor 🙂

Comments are closed.

Skip to main content