Hi, I am curious because I have heard others say this too, but have never quite understood it. I can see why isinteg might destroy a database that is already suspect or damaged. But what I am not clear on is: why would isinteg damage a perfectly healthy database? Is that a fact or an urban legend? Is isinteg really that flaky? Would Microsoft have released it or be recommending it's use if that were so? best regards JW On 12/9/05, ChongJa@xxxxxxxxxxxxxxxx <ChongJa@xxxxxxxxxxxxxxxx> wrote: > > http://www.MSExchange.org/ > > > This is a multi-part message in MIME format. > > You could, it may or may not fix the problem. The isinteg will find > inconsistencies and and try to fix orphaned messages attachments... Keep in > mind though that isinteg should only be run when there is indication of > corruption whether through event logs or other means. Running isinteg on a > healthy db can actually do harm. >