Using a Source Code Management system enables an automated database-change workflow. 

When SQL code is checked in, a trigger or polling mechanism can automatically start a packaging process, which refactors the SQL code files and deploys the resulting changesets to the REF database. 

Projects

A project (also called a Deployment Plan) defines the workflow that SQL code goes through and the database connections for each stage (step) in the workflow. 

You can use different methods to place the a project file hierarchy into source control:

• Directly from local files - Check in the files for the project. The specific method varies by SCM system. You may choose to share database code in the same repository as application code or have it reside in its own repository. 
• Datical GUI - Right-click on a project, then select Team > Share Project. You then select your SCM system and provide more information 

SQL Code

In order to package SQL scripts for deployment, you must set up your SCM for SQL code. SQL scripts are packaged directly from the SCM. 

The Deployment Packager requires a set of folders named as follows. 

<sql_code_dir> # for example, sql_scripts
   archive
   data_dml
   ddl
   ddl_direct
   function
   package
   packagebody
   procedure
   sql
   sql_direct
   trigger

mkdir archive
mkdir data_dml
mkdir ddl
mkdir ddl_direct
mkdir function
mkdir package
mkdir packagebody
mkdir procedure
mkdir sql
mkdir sql_direct
mkdir trigger