Contents

Project Build Overview

Building a project is a complex processing of project scripts, which results in one ready-to-deploy script or several scripts with a batch file.

At first, the project script syntax is checked. If project scripts have syntax errors, the build is stopped.

If the declaration cannot be found, an error or warning is raised.

A warning is raised in the following cases:

• A database object from a schema, other than the project schema, is referenced, and this object cannot be found in the schema
• There is an unresolved reference in the DROP statement
• The user is referenced

In all other cases an error is raised, and the build is stopped. You may enforce the build to ignore errors by selecting the Ignore errors check box in the Build options.

The Build options also include a check box Analyze Pre- and PostDeployment.sql files.

If this option is enabled, PreDeployment.sql and PostDeployment.sql will be processed as common project files. If this option is disabled, these files will be added to the resulting deployment script as is, without parsing.

The check box is clear by default, since the script may contain commands that both the server and the user define as valid, but the script folder does not. This may lead to false error messages.

In the Build options, you can also select either a single SQL script file or a batch script file to be generated.

Eventually, project scripts are processed according to the build order. The build order is defined automatically according to dependencies between objects. The Build Configuration page shows the files to be included in the build.

Note

The project build will delete all SQL files with the same names as project files in the build output directory without user confirmation. dbForge Studio asks for confirmation before deleting any other SQL file. Non-SQL files in the build output directory are not affected by the build. The build output path can be specified in the Build options.

Want to Find out More?

• Previous
• Next