The full text of this article can be read at the following address:
http://www.google.com/support/urchin45/bin/answer.py?answer=28235&topic=7414
databases for each Profile configured within Urchin. These databases
typically reside in the data/reports directory
of the Urchin distribution. By default, Urchin will keep an unlimited
number of these monthly Profile databases. For most small and medium
sized sites, the storage requirements are fairly modest. Because
Urchin reporting does not require access to the raw webserver logs
once they’ve been processed, there is no need to keep the webserver
logs. The “crunched” Urchin monthly databases will be approximately
5-10% of the size of the raw webserver logs that were processed to
populate the Urchin databases, and in most cases this will represent a
very minimal amount of disk space even if all Urchin databases are
kept indefinitely.
If you still wish to remove this data, it can be found in the profile
directory for your domain. You will see quite a few files with
names in the following formats:
YYYYMM-hdata.und
YYYYMM-hdata.uni
YYYYMM-hdata.uns
YYYYMM-pdata.und
YYYYMM-sdata.und
YYYYMM-tdata.und
YYYYMM-udata.unf
YYYYMM-vdata.und
YYYYMM-vdata.uni
Each set of files is the complete database for the given month and year
referenced in the file name. Since these files are only accessed
by Urchin when stats are actually being generated, it is usually safe
to remove them either before or after stats have run. If you
remove some of these files, you can reduce the data that urchin is
actually using for display purposes. Important Note: future major releases of
Urchin are likely to use the data from these databases for reporting
purposes. Therefore, it is recommended that these databases be
retained if you wish to have complete historical reporting for Urchin
after a major version upgrade.