Home Page link  

HQEventLog & TimeStampLog size out of control!

  
Groups | Search | About
User Password
Register Now! Lost Password?

Point-Of-Sale Software - - MS Point Of Sale software discussed here 

get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content  add this group's latest topics to your Google content  YahooMyWeb Yahoo!  Google Google  Windows Live Favorites Windows Live  del.icio.us del.icio.us  digg digg  Add to Netscape Netscape
Subject Author Date
HQEventLog & TimeStampLog size out of control! dizz 05-16-2006
Posted by dizz on May 16, 2006, 11:44 am
Please log in for more thread options
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

Posted by HankSmart on May 16, 2006, 12:22 pm
Please log in for more thread options
Well I do not have an answer for you, I have a similiar problem. Could you
provide the scripts you ran to get the size of a table? Is it a simple SQL
statement or is it something more advanced?

"dizz" wrote:

> 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

Posted by dizz on May 16, 2006, 2:19 pm
Please log in for more thread options
Here is the script:

USE [db_name_here]
DBCC UPDATEUSAGE ( 0 ) WITH COUNT_ROWS
EXEC dbo.sp_MSforeachtable 'EXEC sp_spaceused ''?'''

Substitue the name of your HQ database in the brackets on the first line. I
ran this in SQL Query Analyzer...


"HankSmart" wrote:

> Well I do not have an answer for you, I have a similiar problem. Could you
> provide the scripts you ran to get the size of a table? Is it a simple SQL
> statement or is it something more advanced?
>
> "dizz" wrote:
>
> > 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

Posted by HankSmart on May 19, 2006, 2:05 pm
Please log in for more thread options
Many thanks.

"dizz" wrote:

> Here is the script:
>
> USE [db_name_here]
> DBCC UPDATEUSAGE ( 0 ) WITH COUNT_ROWS
> EXEC dbo.sp_MSforeachtable 'EXEC sp_spaceused ''?'''
>
> Substitue the name of your HQ database in the brackets on the first line. I
> ran this in SQL Query Analyzer...
>
>
> "HankSmart" wrote:
>
> > Well I do not have an answer for you, I have a similiar problem. Could you
> > provide the scripts you ran to get the size of a table? Is it a simple SQL
> > statement or is it something more advanced?
> >
> > "dizz" wrote:
> >
> > > 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

Posted by Nick on July 19, 2006, 7:54 pm
Please log in for more thread options
I know this is late reply, but I am experiencing similar problems.

You can safely delete HQEventLog through the HQ Manager program. Under
VIEW-EVENTLOG. This only stores HQ Client Logs.
I haven't experimented with the TimeStampLog.

"dizz" wrote:

> 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

Similar ThreadsPosted
HQEventLog table size and maintainance May 17, 2006, 9:21 pm
HQ Pricing Control January 6, 2006, 6:53 pm
Logic Control and USB January 22, 2006, 10:20 pm
More control over taxation November 8, 2006, 10:11 pm
Discount Control July 2, 2007, 6:36 am
Control Codes March 21, 2008, 9:46 pm
Stock Control How to...???? August 18, 2008, 6:59 am
RMS or SQL log file has grown out of control April 25, 2007, 5:36 pm
Inventory Control Question April 5, 2008, 3:50 pm
HQ Item Control - CACHE and AUTOGENERATE March 2, 2006, 5:15 am

Contact Us | Privacy Policy
This site is not affiliated with Intuit - makers of Quickbooks and Quicken software
This site is not affiliated with Sage Software - makers of Peachtree accounting software
XML SitemapXML Sitemap