Timeline for Analyze MySQL what needs to be archived
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 24, 2020 at 0:35 | comment | added | protobyte | TY. Separating the PII is a good suggestion for security purposes. However it doesn't really answer my original question. It is sanitized to keep devs from accessing it. Even if it is separate, we'd still have to sanitize all of it, unless we select a subset of records. Which is why I'm trying to calculate what to archive and what is needed in dev environments. I will look into shrinking data types, though I still feel giving dev environment 8+ years of records is not necessary. Plus it would shrink it even more. How does budget gives us more privacy? Prod expenses is only ~1% of dev expenses. | |
| Nov 22, 2020 at 20:45 | comment | added | Rick James | @protobyte - I added more. | |
| Nov 22, 2020 at 20:44 | history | edited | Rick James | CC BY-SA 4.0 |
added 534 characters in body
|
| Nov 22, 2020 at 18:07 | comment | added | protobyte | It may be, but in my case, our RDS bill is 80% of our AWS bill. I am talking about a clone or production which is from a snapshot. Then archive old data for development environments. Right now we have records that go back 8+ years. For developers, they do not need all of this. "How old is old?"; that is what I'm trying to figure out. How can I determine this? How would you suggest? The 3 hrs is because we have to sanitize so much data. If I could sanitize less data, it would take less time for the db to get restored from this snapshot. | |
| Nov 21, 2020 at 1:02 | history | answered | Rick James | CC BY-SA 4.0 |