Importing a Model from a SQL File

From ER/Studio Data Architect
Jump to: navigation, search

Go Up to Importing a Model

  1. Choose File > New.
  2. Select Import Model from and then from the list, choose SQL File.
  3. Click Import.
    Notepad blue icon 2.pngNote: You can also go from File > Import File > From SQL File.
  4. Complete the Import Database SQL File dialog, click OK.
    The import log displays.
  5. Optional. To save or print the log, click Save to File or Print.
  6. If import was successful, click Finish to create the model.
  7. When the Import Status Dialog displays Finished Import, click Close.
  8. Save the new model.

The following describe fields and options in the wizard that require additional explanation.

  • Quick Launch: In the last step of the wizard, you can save settings to a file for later reuse. If you have previously saved such a file, you can load it by clicking the... button next to Select Settings File on page 2 of the Import Model wizard. Then click Go to run the import exactly as before, or click Next to modify the settings. The Wizard Quick Launch data is saved as an.rvo file. The default location for these files is:
To change the default directory for Quick Launch files, choose Tools > Options > Directories.
  • Select a Database SQL File: Type the database file name or browse to the file location and then click Open.
  • Select the target database platform: From the list, select the target database platform.
  • Infer Referential Integrity: ER/Studio Data Architect can infer referential Integrity when none is declared in the database. Click the options that follow to create relationships between entities in your diagram.
    • Infer Primary Keys: If selected, ER/Studio Data Architect infers primary keys from unique indexes on a table. If more than one unique index exists on a table, ER/Studio Data Architect chooses the index with the fewest columns.
    • Infer Foreign Keys from Indexes: If selected, ER/Studio Data Architect infers foreign keys from indexes. When inferring foreign keys from indexes, ER/Studio Data Architect looks for indexes whose columns match the names, datatype properties, and column sequences of a primary key. If the "child" index is a primary key index, it must contain more columns than the "parent" primary key. In this case, an identifying relationship is created.
    • Infer Foreign Keys from Names: If selected and your database contains foreign keys, ER/Studio Data Architect infers foreign keys from names. When inferring foreign keys from names, ER/Studio Data Architect looks for columns matching the names and datatype properties of a primary key. In this case, a non-identifying relationship is created. ER/Studio Data Architect cannot infer relationships where the child column has a role name, instead create a non-identifying relationship and then designate the correct role-named column using the Edit Rolename function; right-click the relationship and then click Edit Rolename.
    • Infer Domains: If selected, ER/Studio Data Architect infers domains from the columns in the database. ER/Studio Data Architect creates a domain for each unique combination of a column name and its associated datatype properties. Duplicate domains with an underscore and number suffix indicate that columns with the same name but different datatypes were found in the database. This can alert you of how standardized the columns are in a database. You can use macros to consolidate domains and preserve the bindings from the inferred domains.
  • Select the Initial Layout Option: Select an initial layout for the data model:
    • Circular Layout or Tree Layout: If selected, provides best performance when reverse engineering large databases. For more information, see Changing Data Model Layout.
  • View Parser: Select a platform-specific syntax interpreter.
  • Summary of Selected Objects: Select an object type to display in the Summary of Selected Objects grid and then review the object type, owner, and object name of all the objects you selected for the reverse engineer.
  • NUMBER datatype: NUMBER or NUMBER(*) you must set the width and scale to *. A width of 0 will be converted to * when generating DDL.

See Also