These settings enable you to define target connection settings and target table locations.

Target Connection Settings

OptionsDescription
Default Table Create DDL TemplateThe default Template used for generating DDL for new Tables created on targets of this connection.
Default View Create DDL TemplateThe default Template used for generating DDL for new Views created on targets of this connection.
Create procedures in same database as table

This setting enables you to specify if the procedures associated with new Tables created on Targets of this connection is created in the same database as the Table objects, or in the RED repository meta database.
This option is not selected (OFF) by default for existing RED repositories, e.g. the Table's stored procedures are created in the RED repository meta database.
If the Table is created in a different Target location (e.g. distinct schema/database in the same SQL Server instance), you can turn ON this option if you want the stored procedures to also be located in the same Target database as the Table object.

  • For new RED repositories, this option is ON by default (e.g. procedures are created in the same location as the Table object). New or regenerated procedures are created in the specified location.
  • Changing this setting has no impact on existing stored procedures. You must Rebuild or Regenerate the stored procedures for the changes to take effect.
  • If the Lock Storage Location option in the Procedure Properties window is set, then the current location of the procedure is retained, e.g. no changes will occur if the Target location of the procedure is manually changed and a Rebuild or Regenerate operation is performed via the Table object's Properties window or from the Table object's right-click Code context menu,
  • If the Target location of a Table object is changed, then both the Re-creation of the Table object (as in previous versions of RED) and the Regeneration of the Procedure object is required for both objects to be moved.
    Refer to Procedure Migration
  •  for details.


Enable Automatic Creation of Indexes

This setting enables you to turn ON/OFF the automatic creation of metadata for indexes when creating new objects. Neither the RED metadata nor the physical index is created, if this setting is not enabled for objects.
This option is selected (ON) by default. You can turn OFF this option for databases that do not have indexes, and if you do not require RED to automatically create metadata indexes for objects.

  • This setting only applies when creating metadata indexes for objects and does not affect existing metadata index records.
  • Turning this option OFF does not delete existing metadata records or the physical index. 


Default Pre-Load ActionThe default Pre-Load Action to use for Load tables created on targets of this connection. Options include:
  • Truncate
  • Execute Pre-load SQL
  • Both Truncate and Execute Pre-Load SQL
  • No action
If Execute Pre-Load SQL is selected, then the SQL statement to execute before the load takes place must be entered—refer to Pre-Load Action in Database Link Load Properties Screen for details.
Column Properties ConfigurationLists all the available Column Properties UI Configurations in the metadata.

Target Table Location [For target-enabled licenses]

OptionsDescription
Add new Target LocationThis option enables you to add new database/schema locations for objects in this connection.
For Greenplum, Netezza, and PDW schema target locations setup, refer to Database source system - Local/Linked Servers or ODBC connection topics, depending on the connection type chosen for the database source.
  1. Click the Add button to add the required target schemas for this connection.
  2. Give the new target a name and then enter the target's schema.
  3. Default schema location(s) for New Tables can also be set from the Tools > Options menu. Refer to Settings > Storage > Target Location for details.


The database and schema names for Custom database connections are used as follows: <database>.<schema>.object name
Leave database name blank if not required. Leave the schema name blank to use the default schema.


  • No labels