Defining Source Systems
Go Up to Data Lineage Workflow
Data sources can originate from models in the active diagram (local models), from external sources imported into the active diagram, or from a data sources created on the Data Lineage tab. You can import the source from *.dm1 files, *.dt1 files, database or SQL files, flat files, and other common application files. Potential sources from the open diagram are found on the Data Lineage tab, which can be seen by expanding Data Sources > Local Models.
Note: Source data imported through the Data Lineage tab only includes information such as table and column name, datatype, nullability, primary key, and column definitions. To obtain more details, reverse engineer the database or import it into ER/Studio Data Architect using the Metadata Wizard.
Contents
Creating a New Source
- From the Data Lineage tab, expand the Data Sources node.
- Right-click Other Sources, and then click New Source.
- Complete the Data Source Properties dialog as required, and then click OK when complete.
The new source appears under the Other Sources node with one empty object node, which may be Tables or Entities depending on the data source type defined. You can edit the new source model by expanding the Other Sources node, and then the new source node. Then, right-click the source object, and select Add Table/Entity to launch the Table or Entity Editor.
The following describe options require additional explanation:
General tab
- General Properties
- Name. The name you give it here appears as a data source in the Other Sources node within the Data Lineage tab.
- Type. Select the source type. This setting affects available options in the Connectivity group. For example, select Relational for a DBMS such as MySQL.
- Connectivity Properties.
- Host, Server/Service, Port. For connecting to an external DBMS. For an existing ER/Studio Data Architect physical model, leave blank.
- DBMS Type, Version, Location/Path, File Type, Encoding. These settings depend on the Type selected above.
Model Usage tab
This is a read-only display of the source defined on the General tab. Ensure that it matches your intentions.
Importing External Source into Other Sources
- From the Data Lineage tab, expand the Data Sources node.
- Right-click Other Sources, and then click Import New Source.
- Complete the Data Source Properties dialog as required, and then click OK when complete.
The new source appears under the Other Sources node.
The following options require additional explanation:
- Page 1 - Please select where you would like to import the source metadata from
- From a Repository based DM1 file. Lets you obtain source from data models and Named Releases managed within the Repository. When you select this option, ER/Studio Data Architect opens the Repository Operation Status dialog box and the Get From Repository dialog box. This process connects to the current Repository Server defined in the Repository settings. The Import Source wizard automatically gets the diagram.
- From an SQL file. ER/Studio Data Architect imports the SQL file.
- Compare against a live database. If you select this option, a page appears where you can select the database and connection type. The connection type can be either ODBC or Native/Direct Connection. For information about connecting to databases, including troubleshooting information, see Connecting to Database Sources and Targets.
- Comparison Quick Launch. The Compare Quick Launch data is saved as an *.rvo file. For information on using the Quick Launch option in the wizard, see Saving and Using Quick Launch Settings.
- Page 5 - Results
- Current and Target Model Display Grid. Between the Source and Target models is a Resolution column. The default merge decision is Merge the data into the new source file. You can click on any item in the Resolution column to enable the decision list. If you want to change the decision, click the list, and then click the new resolution. When you change the default resolution of an object, the decisions of their dependent properties and objects are automatically updated. You can also click the category folders, like the Tables Resolution column to change all the decisions for all the underlying objects in that object category. Use the CTRL key to select multiple items, and then right-click to enable the decision list.
- SQL Difference. To enable the SQL Difference utility, select any difference that is a long text field, such as a Definition, Note, or DDL, and then click SQL Difference to view the differences between the SQL of the models. This utility only allows you to view the differences; difference resolutions are performed on the Results page of the Compare and Merge Utility.
- Filter Report on Results. Create a report of the source content and your chosen resolutions. You can choose to create an HTML or an RTF report.
- You can modify the default display using the options at the bottom of the page.