There is nothing that would help you analyze the DB directly since JR structure is behind the public JCR API. YOu might be able to find something in the jr-commons or in their sandbox but I doubt it. The best shot is probably traversing the website/dms tree and looking at the versions there. Another possibility is to traverse all the nodes in the mgnlVersion workspace. Those are the nodes that are normally hidden behind Magnolia APIs and are really connected to the JCR version space. There you might be better able to do some cleanup, but otoh it is easier to break something. If you go down that way, you need to ensure that all the ops are executed in the SystemContext, otherwise you would not see anything in this workspace.
HTH, Jan On Dec 13, 2010, at 10:44 AM, Andrea Castelli wrote: > Dear Magnolians, > I would like to measure data on my DB. Or better: I want to understand > which are data that are consuming more space than others (inside a > repository). Are there tools or groovy scripts to do this? > > > > I would like to identify the biggest files, the old and big versioned content > and the duplicated data. Any advice? > > > Thank you. > Best Regards. > > > > Andrea Castelli > ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
