Migrating an existing repository to SQL Anywhere

SQL Anywhere is the only supported repository in Sybase ETL. SQL Anywhere 11 is the recommended version for use as an ETL repository. If you are using any other repository from an earlier version of ETL, you must migrate your existing ETL repository to SQL Anywhere 11.

Included with the Sybase ETL Development installation is a SQL Anywhere 11 repository for migration of an existing repository. See “Migrating an existing repository to SQL Anywhere”.

NoteIf you have installed Sybase ETL Server and not installed Sybase ETL Development in your environment, you must manually install SQL Anywhere 11, which is packaged separately with Sybase ETL Server. See “Installing SQL Anywhere as an ETL repository”.

StepsMigrating from an existing repository to a SQL Anywhere repository

Before you migrate:

NoteYou can only migrate ETL 4.5 and later repositories.

To migrate:

  1. Navigate to Start | Programs | Sybase | Sybase ETL Development 4.9 to launch Sybase ETL Development.

  2. Set up the repository connection in the Repository Logon window:

    NoteIf the Repository Login window does not open on launch, select File | Open Repository to open it.

    1. Click Add and enter repositoryMigrate as the name.

      NoterepositoryMigrate defines the job and project objects that are used to implement migration. This ODBC entry is defined during installation.

    2. Select ODBC from the Interface list.

    3. Select repositoryMigrate from the Host list.

    4. Enter dba as the user and sql as the password.

    5. Click Test Logon to test the connection.

    6. Click Save.

  3. Select the repositoryMigrate connection, if it is not already selected, and click Logon. The other default connection parameters are:

    • Client – transformer

    • Client User – TRANSFORMER

    • Password – transformer

  4. In the navigation pane, click Jobs to expand the list of jobs.

  5. Right-click the migrate Repository job and select Job Execute with Parameter Set.

    NoteThe migrate Repository job assumes that the repository tables have been created in the target repository. These tables are already created in the database to which the repositoryNew data source points. If you are migrating to a different instance of SQL Anywhere, make sure the repository tables have been created in that database, using the Repository Test Logon button on the Repository window, before running the migrate Repository job.

  6. Sort the parameter list by clicking the component column header, then to sort the parameter column, press Ctrl and click the column.

    NoteThe Component column should be sorted by destination and source.

  7. The Value column contains a default value of TargetRepos for each of the destination components in the migration projects (migrateCHUNK, migrateDATA, migrateOBJECT and migratePERFORMANCE). Double click TargetRepos and enter repositoryNew to change the value.

  8. Update the Value column for the source components, which defines the required information for the source repository.

    • Database – the name of the database is optional if the source database is defined in ODBC.

    • Host – ODBC data source name definition.

    • Interface – dbodbc

    • Password – database password, if defined in the ODBC definition.

    • Schema – schema name is optional if the source database is defined in ODBC.

    • User – database user name, if defined in ODBC definition.

    The details of the source repository are transferred to the Target Repository.

  9. Click Execute.

    NoteIf your source repository is not accessed via ODBC, change the Interface value to either dbsybase for ct-lib or dbole for OLE DB.

  10. Login to your new repository and verify if your projects and jobs have been migrated successfully.