The Test Data Transfer Tool (TDTT) is designed for transferring data between environments to facilitate testing or demonstration, but not for production data import. It utilizes Microsoft SQL Server's bulk copy program for quick operations, requires specific SQL Server permissions, and necessitates a CustomerSource or PartnerSource account for installation. While easy to use and lightweight with several advantages such as faster data transfer, it does require SQL knowledge and has limitations regarding database integrity during imports.

1. TEST DATA TRANSFER TOOL (TDTT) – Hai Nguyen

2. Agenda
•Overview
•Demo
•QA

3. Goals
This tool is designed to transfer the data
between environments to create test or demo
environments with the latest data.
It shouldn’t be used to import data into the
production environment.

4. Goals (cont)
The Test Data Transfer Tool works by calling the Microsoft SQL Server
client tools bulk copy program, BCP.exe. BCP runs very quickly, thus
this tool runs faster than some other data transfer tools. The Test
Data Transfer Tool does not interact with the AOS.
You must have a CustomerSource or PartnerSource account to be
able to download the Test Data Transfer Tool installer. The installer
must be run by an administrator account.
As of today, you can download the tool from LCS (Life Cycle
Services).

5. Pre-requisites
• To be run on a system with SQL Server client tools installed.
• During import, you must run the tool directly from the
computer that is hosting the database.
• Select & Bulk Insert permissions on the SQL database and
ALTER INDEX permission on the table (this is needed if the
data violates the unique index constraints and you want index
to be
disabled automatically).
• Permission to execute SQL scripts that are executed pre- and
post export/import. These can be found in import and
export directory.

6. PROS and CONS

7. PROS
1. Very lightweight and simple to use tool.
2. Can be installed on any machine that has the SQL Server Client tools installed.
3. Can be handy tool in transferring the data among the different environments (for example
data transfer from production to the training environment).
4. This tool can be used to move subset of the data.
5. The tool can be used to import and export any AX entity but I found it more useful while
transferring configuration data among the environments. (for example module parameters
tables)
6. Fast when compare to other data migration tools for AX.
7. Can export or import data when an AOS instance is not running.
8. Export or import Microsoft Dynamics AX data more quickly compared to other methods.
9. Only minimal changes are made to the data that you import. This feature helps guarantee
that the data is stable over time. For example, the tool never renumbers RecIDs.

8. PROS (cont)
10. The data file format is text-based. Therefore, the data can be compared with earlier versions and
stored in a version control system.
11. The data file format is a standard format that is produced by bcp.
12. Exported data can be filtered. Therefore, specified tables, columns, or rows can be easily excluded
from the export.
13. Differences often occur during development. Because of this feature, data can often be imported
without user intervention, even when the table definitions have changed. For example, tables or fields
that have been renamed do not prevent import.
14. Entity IDs, such as table IDs, class IDs, and extended data type IDs, are updated to match the IDs of the
target system.
15. The tool reads and correctly updates the SYSTEMSEQUENCES table.

9. CONS
1.The usage of this tool requires you to have a SQL related skillset.
Since the tool is actually a wrapper on top of SQL Server Bulk Copy
Program (bcp) that’s why the expert level knowledge of the AX
database schema and T-SQL is a must.
2.Since the tool works directly on SQL Server database that’s why the
tool doesn’t make sure that your import produces a complete or
coherent database.
3.Need to have access to SQL database and can run as Admin
4.Command line and there is no UI

10. Export and import process illustrated

11. Syntax
DP.exe {direction} {directory} {database name} {server}

12. Syntax
Parameter Description Default value
Direction Parameters indicates the direction (Import/Export)
Specify IMPORT for Importing Data and EXPORT for
exporting data.
EXPORT
directory Indicates the directory
• from which to import data (or)
• To which to export data files
Defaults to current directory if not
specified
database The name of the database:
• from which to export data (or)
• To which import data in to.
AXDB
server The name of the sql server on which the database
is hosted
The current computer name

13. DEMO

14. Q&A