Database Designer

The database designer contains the database model imported from the actual database schemas. On top of this, additional metadata can be stored and viewed, adding more ways to describe and document the database model than what SQL Server allows.

The goal of database designer is to speed up the creation and modification of common database entities and their metadata by providing a limited but tailored list of actions and best practices.

Concepts

Database model

The model as it exists in the SQL Server database.

Database Designer model

The model as shown in Database Designer. This includes any changes not yet applied.

Getting started

  1. Perform an Import from database.
  2. If using Softadmin® Map
    1. Perform Import from Map. Use the default settings for the first import.
    2. After the first import make setup the settings according to Softadmin® Map import settings.
  3. Start modeling in Database designer.

Import from database

Imports all changes made to the Database model. Any pending changes are reapplied to the Database Designer model after a import is made from the database.

Apply to database

Applies all pending changes to the database.

Revert changes

Reverts selected changes currently in the Database Designer model.

Interaction with Softadmin® Map

Database Designer will fully replace Softadmin® Map in the future. And if possible most modeling work should be done in Database Designer from Softadmin® version 8.8.0 and forward. Some features may not exist in Database Designer and therefore Softadmin® Map may be used as a complement.

Both Database Designer and Softadmin® Map can be used in the same system during a transitional phase. However both modeling tools should not have ongoing changes at the same time to avoid merge conflicts. Always apply changes and import/synchronize before swapping modeling tool.

Import from Map

The button "Import from Map" imports all data from Softadmin® Map according to the settings Softadmin® Map import settings.

Export System- and function-blocks to Softadmin® Map

Use the button "Export to Map". This makes it possible to export selected system- and function-blocks to Softadmin® Map. This is needed if you plan to model system- and function-blocks using Database Designer but still want to be able to do either all or part of the Table modeling in Softadmin® Map.

Softadmin® Map import settings

Found at "Database designer > Settings > Softadmin® Map import settings". Controls the settings for the "Import from Map"-button. The goal should be to have the setting "Database Designer", but as long as modelling is done in Softadmin® Map it may not.

  1. Table layout. Select the option where you make most table modelling. Once using Database Designer, there is no way to go back to Softadmin® Map without overwriting the data in Database Designer.
  2. System- and function-blocks. It is strongly recommended to use the option "Database Designer" here. To see the System- and function-blocks in Softadmin® Map see Export System- and function-blocks to Softadmin® Map.
  3. Table types. Select the option where you make most table modelling. Once using Database Designer, there is no way to go back to Softadmin® Map without overwriting the data in Database Designer.
  4. Meta data. Select the option where you make most table and column modelling. Once using Database Designer, there is no way to go back to Softadmin® Map without overwriting the data in Database Designer.

Disabling Softadmin® Map

Whenever the you are confident database modeling can be handled using mainly Database Designer, and SSMS for some special cases, Softadmin® Map may be uninstalled.

Known problems

System- and function-blocks

Do not model System- and function-blocks in both Database designer and Softadmin® Map as it will cause conflicts. We strongly recommend using Database Designer for this task. Export System- and function-blocks to Softadmin® Map

Moving function blocks

Do not move function blocks between system blocks in Softadmin® Map. This will cause Database Designer to create duplicates of the function block.

Local database development

Local database development is not supported yet.

Database Designer settings

Found at "Database designer > Settings > Database Designer settings". Controls the configurable behavior of Database Designer depending on project specific rules.

Key differences from Softadmin® Map

  • Database Designer is built into Softadmin® making sure the technical requirements are the same as for Softadmin®.
  • Does never stages any changes in the import-phase, only when the user interacts with the GUI.
  • Stages changes in the order the user made them instead of trying to determine the order itself. Database Designer does however merge deploy scripts to ensure effective and clear deploy scripts as well.
  • Does not store important information only in its staging data, making it possible to always make a new clean import without losing data.
  • Allows manual edit of scripts for actions not supported in the GUI, or to work around bugs. These changes can the be imported using the regular import.