Oracle Visual Builder comes with a built in database that is used to store data for your business obejcts (and your apps metada too). That DB, however, is limited to 5GB in size and also doesn't enable you to access the data in the objects using regular SQL. Luckily, you can point Visual Builder to use another Oracle cloud database including the new Oracle Autonomous Transaction Processing (ATP) database - which will give you more space and direct SQL access to the objects VB creates. You can even use a Free Forever Oracle ATP which will get you 20GB of storage for free. In the demo below we show you the steps to take to do this switch.
The switch over is quite simple and is done with a simple two step wizard in your VB instance settings. You'll need to provide the connection information to your DB - for an ATP DB this would include the wallet.zip file with the connection info. VB will then do the work for you switching to use the new instance. More info on the process is in our Visual Builder Administration Guide.
One additional step you will need to do in the wizard is to backup (export) any apps you want to keep around.
(Important note - if you have live applications already on the instance before migration - make sure to backup the data in their business objects using the export options in the Visual Builder data manager. You'll then be able to import that back into the new apps you'll create from your backup).
Visual Builder automatically manages the schemas and tables it uses for apps and business objects in your new DB - so you don't need to do anything further.
If you would like to access the business objects using SQL, you'll find that VB creates users/schemas with names starting in VB_ followed by randomly generated strings. With a bit of inspection in the data dictionary you'll be able to find the users that represent specific apps. Note that you'll see separate schemas for dev, stage, and published instances of an app. The schemas for the dev and test instances will be re-created with different names with every new version of the app that you'll create. The schema name for the published app can stay fixed if you indicate to not replace the data in it when publishing new versions.
Here is the flow of steps in a quick video: