add entry for snowflake development databases, including retention policy
Why is this change being made?
Clarifies the use of development databases in snowflake, adds information and links about development and development databases cleaning
corresponding change to data project https://gitlab.com/gitlab-data/analytics/-/merge_requests/10434
Author and Reviewer Checklist
Please verify the check list and ensure to tick them off before the MR is merged.
-
Provided a concise title for this Merge Request (MR) -
Added a description to this MR explaining the reasons for the proposed change, per say why, not just what - Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
-
Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI) - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
Maintained by
section on the page being edited - If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
- The when to get approval handbook section explains the workflow in more detail
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
For transparency, share this MR with the audience that will be impacted. -
Team: For changes that affect your direct team, share in your group Slack channel -
Department: If the update affects your department, share the MR in your department Slack channel -
Division: If the update affects your division, share the MR in your division Slack channel -
Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR - For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter
-
Commits
- add entry for dev db
Merge request reports
Activity
added HandbookContent label
assigned to @jjstark
- Resolved by Justin Stark
- Resolved by Justin Stark
- Resolved by Justin Stark
Using combined codequality.json
⚠ ️ Pipeline Failure - Linting ErrorsOne of the linters has reported errors and as a result the pipeline has failed. Once the pipeline completes, you'll find the code quality report above which can link you to where the error is in your code. Additionally, below you'll find a table of the errors. The table has links to the lint rules so you can find more information on how to fix the issue(s).
Rule File Line Error MD012 content/handbook/business-technology/data-team/platform/dbt-guide.md 53 Multiple consecutive blank lines [Expected: 1; Actual: 2] If you need more help please reach out on Slack in #mr-buddies.
Using combined codequality.json
⚠ ️ Pipeline Failure - Linting ErrorsOne of the linters has reported errors and as a result the pipeline has failed. Once the pipeline completes, you'll find the code quality report above which can link you to where the error is in your code. Additionally, below you'll find a table of the errors. The table has links to the lint rules so you can find more information on how to fix the issue(s).
Rule File Line Error MD012 content/handbook/business-technology/data-team/platform/dbt-guide.md 55 Multiple consecutive blank lines [Expected: 1; Actual: 2] If you need more help please reach out on Slack in #mr-buddies.
- Resolved by Justin Stark
Post to slack once merged
We've just merged an update to our weekly snowflake cleaning DAG that drops all tables in development databases that are 80+ days stale. Additionally, we've updated the handbook to clarify the expected use of development databases. You can query
PROD.DATA_QUALITY.STALE_DEV_DB_TABLES
to see if any tables in your development database will be affected.cc: @dvanrooijen2 @pempey
mentioned in merge request !7094 (merged)
- Resolved by Justin Stark
Using combined codequality.json
⚠ ️ Pipeline Failure - Linting ErrorsOne of the linters has reported errors and as a result the pipeline has failed. Once the pipeline completes, you'll find the code quality report above which can link you to where the error is in your code. Additionally, below you'll find a table of the errors. The table has links to the lint rules so you can find more information on how to fix the issue(s).
Rule File Line Error MD022 content/handbook/business-technology/data-team/platform/dbt-guide.md 56 Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Above] If you need more help please reach out on Slack in #mr-buddies.
- Resolved by Justin Stark
mentioned in commit 6fa7cea2