Thanks Robert. That helps. I didn't know about the re-index. I just read a case study that said the index took 35 days. So doing a re-index is not something I'd want to do often.
My TAM also finally responded with an article on sizing. I've only quickly read it, but it looks like the live example they gave would be about 48%. That's not too awful until you plan for 2x for the re-index. Kevin On Mon, Jun 23, 2008 at 1:06 PM, Robert Cato <[EMAIL PROTECTED]> wrote: > > The rule of thumb from the MOSS class I attended was 30%. The big gotcha is > that if you make a change that requires a re-index it makes a new index file > before it removes the old one. You better make sure you have plenty of > space. There are search add-ons for the non-Microsoft file types (like Adobe > pdf for example), if you add a new add-on it initiates a re-index. > Still working out the details of our deployment to happen later this year, > but the instructor said if you do nothing else read the search chapter in > the administrators guide multiple times before you implement search, mostly > because you want to avoid a re-index. > > Hope that helps, > Robert > > On Mon, Jun 23, 2008 at 11:39 AM, Kevin Lundy <[EMAIL PROTECTED]> wrote: > >> Has anyone implemented MOSS for Search on a sizeable file shares? >> (multi-TB) >> >> What I'm looking for is some guidance on estimating the index size. I'm >> putting together a project for upgrading to MOSS and the index size is the >> one piece I can't find any help on. Maybe it is just my search skills on MS >> site. >> >> I've used the Capacity Planning tool and it doesn't mention disk space. >> I've downloaded many whitepapers, including the MOSS for Search Guide. >> >> Any direct guidance or just better search terms would be appreciated. >> >> Kevin >> >> > ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
