Archiving and Purging

, ,
1

Hi,

In WebMethods71_TN database
Tables:
dbo.ARCHIVE_ArtivityLog
dbo.ARCHIVE_BizDOC
.
.
.
.
.
.
.
dbo.Archive_WorkTable…
Ineed to develop some scripts so that based on it,
It should archive these tables day to day…and delete the old stuff…

Can u suggest me how to work on this…
Should i need to create new databse,tables…and write the scripts…so that i can schedule that daily…and it gonna archive…and i need to delete the data from orginal archive tables…

Its urgent plz gimme some suggestions…and can anybody help for scripts…sql server 2005

2

Folks, I should not use TN builtin services to archive and purge…I need to do it on databse level…

3

Why not?

4

Hi,

Currently, i archive is going on using wn.tnarchive, from webMethods,…Inorder to not involve, webMethods in archiving, i need to be done on databse level…

5

Is it something your internal decision not to burden the IS job for this activity or something? :slight_smile: On a side note it should run fine though!

6

Yes its the decision taken to reduce burden on IS instead of archiving from webMethods, archiving at database level…can anybody come up with suggestions

7

The archive & Delete services provided by SAG are also supported by them, so if there is a problem you can call for support.

Using self developed scripts means you are accessing the internal db structure of a product internal db structure, which is usually not supported, so everything is on your own risk including that your TN stops working.

I would not recommend such n approach. If you want to do it neverthelesse I would recommend approaching SAG support or professional services for providing the scripts.

8

I agree with mwroblinski’s points above.

However, the DB tables are not complicated. Do an analysis of the tables and determine what you want/need to do.

I would recommend avoiding doing an archive of the tables (copying the data to another set of tables) since that is largely useless. None of the wM tools will be able to present that data and moving the data back into the live tables can be somewhat troublesome. I usually recommend simply deleting old data and having a relatively short time period for what is considered old–30 to 45 days should be sufficient. The TN DB should not be used for long-term storage.

9

I also agree with mwroblinski’s comments!..Most commonly 60 days worth of data would be enough and old data can be archived to get faster query results/performance:

HTH,
RMG

10

thanks to everybody

11

Hi,

Is it possible to have TN Table and TN Archive Tables in different shcema? If yes, how will TN Archive process will work in this approach? Please share your thoughts on good/not approachable implementation. We are trying to keep TN DB and TN Archive DB seperate if possible.
Thanks.

12

You can do it using by writing external archive script not with using TN built-in Archive services.Approach your DBA for more help:

HTH,
RMG

13

Thanks for reply. But can you please tell me if it will be good approach? or is it better to go with in-built services?

Any thoughts?! :slight_smile:

14

Built-in services will work only with same db/schema.The other approach you are looking is take some DBA help:

HTH,
RMG

15

Thanks for your replies. We have created ARCHIVE tables in same schema now. After that when I am trying to execute archive built-in service, I am getting below error:
java.sql.SQLException: An attempt was made to access the SQL statement archive.del.allevents.before.this.time, which was not defined in the configuration file

Am I missing anything? We just ran DB component configurator to create schema.

Please suggest.