Hello, I know the reason now that this has occurred - BDC is writing audit entries into this table (which is a default setting) and there doesnt appear to be any automatic management around this process. I have seen many responses to the above table growing out of control and what has been provided as the answer which is to add <Property Name="Audit" Type="System.Boolean">false</Property> into the entity section of the app def file for the BDC to stop it from logging to this table. My question is how can this table be trimmed or does this actually happen automatically when the BDC app def is updated? I have tried all the tools that I can find around trimming audit entries such as: stsadm (wont work as this table resides within the config db not a content db), codeplex solution called AuditLogTools which again does not appear to work against the config db. A previous post warned against trimming this table manually through SQL which doesnt leave many options here. It would be good however to have a definitive answer here as to what should be completed which I cant seem to locate out there. I am working with a x64 MOSS 2007 SP2 CU Nov 2009 (or roundabout) environment. Any feedback on this is appreciated. Kind regards, Dan

Can you try this to control your audit storage?: http://bit.ly/fEXUEu It is an Romanian article translated in English with G.Translatehttp://valygreavu.wordpress.com/

Thank you for your response. The link you provided relates to content databases and the auditdata table which is not the problem I am working on. I am refering to Config database and the audevent table. I have raised this with Microsoft directly to determine the best course of action.