Loading Foreign Objects into SQL Server

System Administrators can use this procedure to load adapted data into a 3DSpace SQL Server database.

When data is available in 3DSpace via an adaplet, the foreign objects have null values for originated and modified dates, unless you map them to metadata in the other data source. These values remain null when SQL Loader loads the data.

Before you begin: Back up your system before executing loader.bat.
  1. Create any new 3DSpace local vaults to hold the newly-loaded objects. You can also use existing vaults.
  2. Create the load files with the following MQL command: 

    export vault SOURCE into vault DESTINATION[{,DESTINATION1}];

    Where:

    • SOURCE is the foreign vault on which the LOAD utility is to operate.
    • DESTINATION is the name of the 3DSpace local vault(s) into which the data is to be loaded. You can provide a comma-separated (no spaces) list of vaults. If more than one vault is listed, the loader uses a round-robin algorithm unless the mapping file includes vault statements in the table definitions.

    This command creates a series of files in the default directory in which MQL is running:

    • .dat data files
    • loader.bat to invoke the LOAD utility

  3. If you use the MS SQL utility to import the data from the generated loader file, manually edit the file as follows:

    Replace DBNAME, -UUSER, -PPASS with the sql server database's name, login user and login password.

  4. On the database server machine, execute loader.bat on the command line: 

    % sh loader.bat

  5. Check the default directory for files named *.msg. These files describe any problems encountered during the migration.