Analyze Domo Datasets with Large Row Count

[johnny-jesensky-adhoc]

Description

We need to get an understanding of where we are with our Domo usage for the current contract year.

The migration to GA4 created a lot of activity and data movement in our instance, this ticket is to get an assessment of the following, most notably on data rows.

Tasks

Identify the counts for the following in our Domo instance.

• Data Rows We can likely us this dataset to help identify details on each.

---

Tasks

• [x] Review datasets that have greater than 5M rows.
• [x] For each dataset, review it, including cards attached, downstream data flows, and last updated date.
• [x] For each dataset, add comments in column K based on findings.
• [ ] In Column L, leave a recommended action -- this might include something like Keep -- all rows needed, or delete, or investigate in BigQuery -- let's try to be as thorough and definitive as possible. We ultimately want to get our row count down, and see if there are obvious areas we can remove a dataset, or if we need to trim it

Artifacts

• Domo Tables

---

Acceptance Criteria

• [x] We have an accurate count of datasets that are used, with row count.
• [x] Findings have been consolidated in spreadsheet
• [ ] Findings reviewed with the rest of the team.

[johnny-jesensky-adhoc]

@ChristineYoungZA, @Blivaditis - This is the spreadsheet I want to talk through on our sync on Monday -- want to review our datasets by row count, which ones have no cards associated with them, and ultimately flag whether we should keep as is, delete, or possibly optimize.