# MySQL prog2 — Data Freshness Results
# Date: 2026-09-07

## Actual Data Timestamps

| Database | Table | Column | Latest Data | Age |
|----------|-------|--------|-------------|-----|
| ecommerce | tokopedia_product | updated_at | 2019-06-25 | **6+ years** |
| ecommerce | shopee_product | updated_at | 2019-07-02 | **6+ years** |
| pharmanet | m_user | LastOpened | 2019-02-25 | **6+ years** |
| century_emember | M_RelasiMember | Relasi_LastUpdate | 2019-10-05 | **6+ years** |
| absensi | hadir | Absen_In | 2020-06-22 | **5+ years** |
| purchasing | bpom_products | updated_at | NULL | **Never updated** |
| apps_transaction | detail_transaction_owner | LastUpdated | 2023-04-20 | **2+ years** |
| sayasehat | article_tb | updated_date | 2018-02-22 | **7+ years** |

## Analysis

| Database | Status | Notes |
|----------|--------|-------|
| ecommerce | **STALE** | 2019 data, no updates |
| pharmanet | **STALE** | 2019 data, no updates |
| century_emember | **STALE** | 2019 data, no updates |
| absensi | **STALE** | 2020 data, no updates |
| purchasing | **STALE** | NULL, no updates |
| apps_transaction | **RECENT** | 2023 data, some activity |
| sayasehat | **STALE** | 2018 data, very old |

## Conclusion

**Most data is STALE (2018-2020).** Only `apps_transaction` shows recent activity (2023).

This is a **legacy/backup server**, not a live production system.

## Implications

1. **Data is old** — 5-7 years stale
2. **Not live production** — backup/archive server
3. **Leverage limited** — old data has less value
4. **Negotiation angle** — historical data, not current operations

## Recommendation

Focus on **historical data value** for negotiation, not current operations threat.
