Sync relational model data

The LLBLGen Pro designer contains a central place where relational model data and entity model data are synchronized with each other: the Sync tab.

It is used for both synchronizing the entity model with an updated database schema in your database (Database first) as well as synchronizing your relational model data in your project with an updated entity model (Model first). In this tutorial we'll be using the latter, we'll using Sync to adjust the relational model data in the project based on the changes we've made to the entity model.

Updating the relational model data with our changes

  • Start the LLBLGen Pro designer. Either use the Programs start menu, Windows search or double click the LLBLGenPro.exe in the installation folder to start the LLBLGen Pro designer.
  • To open our tutorial project, select it from the Recent Projects list on the Home Tab, or select File -> Open Project... from the main menu, or select the project from the File -> Recent Projects... menu.
  • From the menu select Project -> Sync Relational Model Data or press F5. The Sync tab opens.
  • Your project contains a catalog, schema and tables already. As we're going to use model-first, the Sync source values for the catalog and schemas have to Model or Mixed. If they're set to Database, change them to Model.
  • In the list of Available Sync Tasks, there's one, enabled sync task created for you. To perform it, simply click the Perform Tasks.. button.
  • The Designer will now create a new table based on the newly created Employee entity. It will also create a new field RequiredDate in the Order table. Additionallycatalog it will create a new FK constraint for Order m:1 Employee. It will also create mappings for these new elements. These changes are shown in the log after the Sync task has been completed.

Next step

This relational model data is not in your database server yet. It's only in your project. In the next step we'll export the created elements as a DDL SQL update script so we can update the database physically in our database server: Create DDL SQL Script.