There are 2 methods for patching your database – using the Patch Builder in the legacy developer portal or placing the patching scripts in your patch archive.
1. To perform the database patch through the patch builder, begin by accessing the overview for your current application version and click the Create New Version link.
Once your version has been created, click the Create Patch link.
This will bring you to the patch builder page. Under the Application Persistence folder in the left pane, click on Scripts. Expand Scripts in the right pane, and right click on ApplicationProvisioning_Script.sql. You will be given an option to Patch SQL Scripts. In this window, you have the ability to upload your schema or data patching scripts.
Once you have uploaded your patching scripts, you must also specify and upload the application version archive you wish to use to complete the patch.
2. You can also patch your database by placing your patching scripts directly in your application archive. The scripts must be placed in the Scripts folder within the Persistence folder in your application archive. In order to take effect, they must be listed in the Deployment Manifest with the proper path and script type information as per the example below. They should also be listed in the order in which they should be applied. For multi-tenant applications, an updated Tenant provisioning script can be included in your patching archive. Please note that changes made to Tenant provisioning scripts will automatically affect only new Tenants. You can make changes to existing Tenant data through a data patching script. Other than patch scripts for the application provisioning script and an updated Tenant provisioning script, you must omit any database scripts from your patching archive (other items, such as updated stored procedures, may be included). For more information regarding the various types of scripts and when they should be used, please click here.
<!--Valid values for persistencPatch type: "SchemaScript", "DataScript", "SharedSchemaScript" (mssql only), "SharedDataScript" (mssql only), "Binary" -->
Follow the steps above in option 1 to create a new version of your application, but instead of utilizing the patch builder, just upload your application archive containing your patching scripts.