Sometimes it is necessary to make manual changes into database environments.
For example, a release went out to PROD environment, however, there was an issue which impacted the PROD database. The issue is immediately root caused and the solution is applied manually to PROD database. How then do you make Datical aware of those manual changes?
Note that any manual changes made to a Datical-managed environment should ultimately be deployed to all environments in the pipeline. This will allow the pipeline to remain in sync with respect to changes deployed over time.
Solution Overview
Start by capturing the manual change made in PROD in a SQL script. Commit the script into sql_code SCM repository so that it can be packaged, converted into a changeset and deployed (i.e., backfilled) into all other environments.
Since PROD environment already contains the change, there is no need to deploy the changeset. Instead, you will use Datical's "Change Log Sync" feature to mark the changeset as EXECUTED in PROD environment. This will create an entry in PROD's tracking table (DATABASECHANGELOG) which allows Datical to become aware that the change from this changeset already exists in PROD.
Step-by-step guide
Related articles