Data Management > SQL DB or Folder Clones

This Task will allow you CLONE Multiple Tables at a time

Options :

Clone a complete SQL DataBase (to same or different SQL server) - all the Tables contained in the selected DB will be offered for cloning

Clone a complete FOLDER on your machine - all the TPS and or DAT Files contained in this folder will be offered for cloning

(the folder can contain Tables with extensions declared in DMC and those will be associated to their "parent" format)

If you select a FOLDER level cloning task then DMC will scan it and warn you if duplicate names are found (ie a TPS and a DAT with the same NAME on HD) as this would cause problems when cloning.

This allows you to change the File NAMES (or to delete one) to allow this Folder to be selected.

or if you are cloning an SQL DataBase

(in this case the filled Tables only are pre selected for you)

All the Tables are pre selected for you (icon on the left of the Table Name)

A double-click will toggle selection or you can use the Tag All UnTag All buttons

Select the DESTINATION DataBase you want to use (double-click)

This will display on screen the next steps required

Task Options :

Create a NEW DataBase

DMC will create a New DB on the selected SERVER (and also create an ODBC connection for you to match)

You must then enter the DB NAME in the entry field

TXD Export

DMC will generate a single TXD or DTCX (selectable in a popup message) of ALL the Selected and Cloned Tables STRUCTURES allowing you to IMPORT ALL table definitions in your Clarion DCT in one step.

Create Profiles

DMC will create ALL Profiles corresponding to the current task on ALL the Selected Tables allowing you to run or export this Project to use with the RT engine

Run created Data Profiles

If you want to immediately Transfer all DATA from your source to the newly cloned tables, check this option box and at the end of the cloning task DMC will close and reopen to run ALL data Transfer profiles generated and ALL your Data will be transferred.

TPS Superfiles & Passwords

If you have a Password protected file in the folder, DMC will ask you for it and STORE it in the special password file it use (to avoid redefining it each time)

If you have a TPS SuperFile in the Folder, DMC will open up another screen with ALL the Tables contained in it to allow you again multiple selection (like in this screen)

ALL Tables will be pre selected again for you and you can of course double-click on any table to toggle or use again the relevant tag All and UnTag All buttons for your selection

When you click on Start the task is launched

General Rules applied during this multi table cloning Task

All the Names are stored in a Temp Q (and all the Table Names contained in a SuperFile also) - the SuperFile tables are PREFIXED with the TPS Name so as to easily find them and to avoid eventual duplicates

All the KEYS declared in ALL tables are also stored in a temp Q and in case of a duplicate (some sql server do not allow two tables to have the same KEY NAME) then they are dynamically PREFIXED with the first 3 letters of the Table they belong to (ie : ByName will become KEY_CLI_ByName when the table Name is Clients or PK_CLI_ByName if it is a primary key)

If a table cannot be cloned (for whatever reason) the task will NOT be stopped but this error will be logged and displayed on screen and the Next table treated.

The column NAMES will NOT be prefixed (as per DMC settings) to avoid too many confusions BUT this compels you to clean out some Column Names BEFORE starting this task in some sql servers!

This is the screen displayed at the end of the task which gives you all relevant in formations on all the Table cloning's.

In case of an error it will be displayed and flagged in RED.

You can also start a NEW Cloning task by changing TABS.

If you defined the task to Create the Profiles this is what you will find in the Projects & Profiles module

A Project is created named as per the FOLDER or DB Name selected and it contains ALL the Cloned tables profiles

You can Export this project and ship it to your clients to use with the RT engine.

NOTES

We recommend you to Restore each and every profile and run it before shipping it to your end-users

We recommend you during these test phases to do all your mapping Options also before you ship the project

THIS TASK IS RUNTIME ENGINE COMPLIANT

If you need to perform this task on your clients machines , then SAVE it as a Profile when all is defined and use the Runtime Engine to run it from your application

The different settings on source - destination Folders (even Table Names) plus some ODBC settings like User Name and Password can be changed dynamically from your application to meet your requirements