HQEventLog table size and maintainance


D

dizz

I am Running RMS HQ with 38 stores and growing. Each store has two POS lanes
and we don't do a large volume of transactions in any given day. The size of
my DB is concerning me, so I ran a query that returns the size of each table,
and what I found is that 95% of the size of my HQ DB is contained in
"HQEventLog" and "TimeStandLog". What I want to know is 1. Would there be
any long term problem in periodically purging anything in either/both of
these tables that is older than 30 days? 2. What would be the best way to do
this (script to use and any suggestions for automation would be great). Just
to give you an idea, the current size of the HQEventLog table reports at
2.2GB and the TimeStampLog at 903MB.

Thanks,
Brandon
 
Ad

Advertisements

J

Jeff

Brandon,

If running 1.3, HQ Manager | View | Event Viewer | red X | select the dates
you wish to delete


I am Running RMS HQ with 38 stores and growing. Each store has two POS lanes
and we don't do a large volume of transactions in any given day. The size of
my DB is concerning me, so I ran a query that returns the size of each
table,
and what I found is that 95% of the size of my HQ DB is contained in
"HQEventLog" and "TimeStandLog". What I want to know is 1. Would there be
any long term problem in periodically purging anything in either/both of
these tables that is older than 30 days? 2. What would be the best way to do
this (script to use and any suggestions for automation would be great). Just
to give you an idea, the current size of the HQEventLog table reports at
2.2GB and the TimeStampLog at 903MB.

Thanks,
Brandon
 
D

dizz

Jeff,
Thanks - I am running 1.2 - but the same options exist - any reason I can't
do it in 1.2 (we have been told to hold off on the upgrade to 1.3 by our MS
Partner until they are done testing with our customization since we have such
a large install base)...

Also a follow up question - will this not only remove the data, but shrink
the free space in the DB after, or will I need to run a shrink after?
 
Ad

Advertisements

J

Jeff

Dizz or Brandon,

Didn't remember if it was in that version too.

I would run a shrink after as I doubt the program would on its own.

Being safe, backup before the delete and again before the shrink!!



Jeff,
Thanks - I am running 1.2 - but the same options exist - any reason I can't
do it in 1.2 (we have been told to hold off on the upgrade to 1.3 by our MS
Partner until they are done testing with our customization since we have
such
a large install base)...

Also a follow up question - will this not only remove the data, but shrink
the free space in the DB after, or will I need to run a shrink after?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top