When it comes time to test your latest database application, Teradata Data Mover (DM) can easily be used to grab real world data from your production system to populate your test system.
Step 1: Start by opening up Teradata Viewpoint in your web browser. Log-in and bring up the Teradata Data Mover portlet.
Step 2: Click on the “New Job” link located in the upper right corner.
Step 3: Pick your production system name from the “Source” drop-down box. Then pick your test system name from the “Target” drop-down box.
Step 4: Use the object browser on the “Source” tab to select the database objects that you’d like to pull from your production system.
Tip: If you don't see the objects you expect, click the icon next to the parent database's filter box and make sure the proper object types are selected. Only the object types with check marks next to them will be shown in the object browser.
Don’t want all of the data from a production table? You can choose to grab only a subset of the table’s rows by doing the following:
1. Move your pointer over the table’s name in the object browser. Click on the down arrow that appears to the right of the name. This opens a submenu for the selected table.
2. Specify a SQL expression in the text box labeled “Include only where”. This expression will be applied in the WHERE clause when Teradata DM extracts the rows from the production table.
3. Select one or more key columns from the option box at the bottom labeled “Key columns”. These columns are used to uniquely identify rows when applying them to the target table on your test system.
Using a different parent database on your test system? You can choose to relocate a table being moved by doing the following:
Want to use a different table name on your test system? You can choose to rename a table being moved by doing the following:
Want to minimalize impact to the production system? You can choose to extract data from the production table without placing a read lock on it by doing the following:
Note: A much less restrictive access lock is still placed on the table using this option. This will allow changes to occur to the production table during the extract process which may result in inconsistencies in the data being moved.
Do the objects being moved already exist on the test system? To allow Teradata DM to overwrite existing objects on your test system, do the following:
Step 5: Click the “Save” button at the bottom to move to the “Save Job” page.
Step 6: Provide a name for this job in the “Job Name” text box.
Step 7: Provide Teradata user credentials for Teradata DM to use for extracting data from your production system in the “Source” credentials column. Do the same for your test system in the “Target” credentials column.
Step 8: Click the “Save” button to save this job.
Step 9: Run the job by clicking the downward arrow next to the job name and selecting “Run”.
A status screen showing the progress of your job will pop up and that’s it! Once the job is completed, you have successfully populated your test system and can begin your application testing.
Thank you for the screen shots. Regaring credentials (Step 7) I haven't figured out how to update them after my account password change. Can you give us a screen shot of that?