Transactions reason for fast growing local DB

niteshnav

I have the problem with the fast growing local DB in the Retail Infostore system. I wish to track all transactions or logs getting generated due to transactions, which may be redundant and can be deleted from the system. What could be the right way of doing it?

bobnavision

BR,

I would advise you to write a dataport and export the Transaction Table on month basis, Say for Jan'06 - export one text file to safe folder.
you will have one CSV/Text file for each month.

Delete the transaction table data which is 30 or 60 days old.
Maintain only one or 2 months data in these transaction tables.

Also what you can do create a new exactly same as Transaction table in DB. So that if some one wants to see old data,he can import that month data in to this table and analyse it.
You need to write separate dataport for this table to import.

This will be the first step I would take.

Cheers \:D/

ovicash

bobnavision wrote:

BR,

I would advise you to write a dataport and export the Transaction Table on month basis, Say for Jan'06 - export one text file to safe folder.
you will have one CSV/Text file for each month.

Delete the transaction table data which is 30 or 60 days old.
Maintain only one or 2 months data in these transaction tables.

Also what you can do create a new exactly same as Transaction table in DB. So that if some one wants to see old data,he can import that month data in to this table and analyse it.
You need to write separate dataport for this table to import.

This will be the first step I would take.

Cheers \:D/

There are two different things, change log and transaction log.
If you want to reduce the size of the tranzaction log you could truncate the file. Search the forum for instructions

bbrown

Which database are you using (native or SQL)?

Can you be more specific about your problem?

niteshnav

Thanks brother..

i am using native as local db & SQL at HO.