We recently ran into an issue where our ePOeventsMT table got to the hundreds of millions of rows and using about 1.5TB of space.
We have solved this issue now but I want to prevent this situation from occuring again. I've been looking at the different options and have come up with about three so far.
1) Use a roll up server to move the older events to a seperate "reporting" ePO server
2) Move all the older events into ESM/SEIM
3) Do some funky stuff within SQL to remove older events.
The idea being that, say once a month, I run a job to move/copy anything older the 90 days out of the live database then delete them. Thereby keeping the live database a manageable size, but also keeping the events. The events need to be kept for security / contract reasons.
How have other people done this? Is that another better way?
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.