Projects & Changes
Projects and changes form the lifecycle management of Yres: categorize work and move changes safely from dev to prod.
Changes
A change categorizes modifications to the data warehouse (updating tables, adding scripted objects). Changes are released and then installed on other environments, so environments stay in sync.
- A change has a due date, which must be on or before the due date of the parent project.
Project Overview
A project groups changes within an environment. It has a name, description and due date.
- A project cannot be deleted while it still contains open changes.
Scripted Objects
Manage custom SQL objects not generated by Yres (your own tables, stored procedures, functions). They are added under a change and can therefore be released/installed along with it. For a custom table you choose with "With table content?" whether the content is included.
Install Changes
Install changes to an environment (e.g. test → prod) via the dropdowns at the top.
- Reimport → calls
[Change].[spImport]: re-fetches the change/project data, including dependencies and content. - Reinstall → calls
[Change].[spInstall]: installs the change on the environment.
Release Changes
Makes a change available for installation.
- After releasing, a change can no longer be edited.
- Yres blocks releasing if the change contains content that another change depends on (the error message names the dependent change(s)).
Change content can be viewed as a diagram (tree structure source → schema → table per source; handy with many objects) or as a table (per object: load type, delta column for delta load, behavior if the object already exists).
Since v1.53 you can choose to include dependencies and/or content when adding to a change, and include existing database objects directly from the object tree into a change.