EIM 4.3 - Archive Jobs and Purging

Unanswered Question
Aug 30th, 2010


I'm looking up setting my archive jobs, and it looks like you have to manually go in and delete the old completed archives when it comes time for you to want to purge the data.

I can't possible think you would need to manually control running these jobs to maintain a safe database size!

Does anyone know if there is an automated way of doing this?



I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)


I have set up the archive jobs for my primary EIM customer. If you have Advanced and multiple departments, each department has an archive job. The system has been running for over a year and has been archiving away, but I have no idea of the size used. Let me shoot over there and check.

It's 5.5GB and 50% full. Active is 3GB and 66% full.

I have 4 x 72GB drives in a RAID 1+0 arrangement, so a D: partition size of 136GB. I have 115GB free (and some temporary DBs to be removed).

The C: drive is the OS and Programs, including MS SQL.

What sort of box do you have? What archive usage are you seeing?

To be honest I had not looked at how to truncate the archive.



BarryMclellan72678_2 Mon, 08/30/2010 - 13:38

Thanks Geoff,

I think I am totally cool on the size. This is what I am running below:

HP ProLian DL380 G5 High Performance

Quad-Core Xeon X5450 3 GHz 2 CPU


Raid 1: 2 X 73gb raid 1 – configured as OS

Raid 10: 4 x 146GB 15K 6G 2.5 SAS DP HDD

I was just surprised that at some point, your database will actually fill up, unless you run those purge jobs (deleting your old archive jobs). I would think this would be more automated, where if you go over a percentage, it truncates.



This Discussion