Prev Next

Migrating OLEDB/ODBC connections to Native

With the introduction of Native connections in Pro Cloud Server v5, Sparx Systems would suggest that all Database Managers defined with either a OLE/DB or ODBC drivers be replaced with a Native Connections at your earliest convenience.

At this stage the migration process is a manual process.

Prerequisites

  • A DBMS database server
  • A database defined in the database server with the necessary table definitions
  • You know the database user credentials that have the correct access permissions, such as SELECT, UPDATE, INSERT, EXECUTE and DELETE

Native connections offer the following Advantages

  • no need to install any 3rd parties drivers (in most case)
  • no need to create any ODBC DSN
  • PCS connection strings contain all necessary connection details
  • native connection strings work for both 32 and 64 bit architectures

Migrating OLE/DB based connections

An OLE/DB connection string should contain all the necessary details, therefore the migration process consist of the following steps:

  1. open the Sparx Systems Pro Cloud Server Configuration Client
  2. select the OLE/DB based Database Manager within the list
  3. click the Edit button, to review the connection details of the Database Manager
  4. make a note of all settings on the Configure Database Manager screen, as well as the extended ones for Run Scheduled Chart Generation and Periodically Generate Diagram Images for WebEA & Prolaborate
  5. make a note of all database settings (as defined in the connection string). ie Server Name, Port, Database Name and User.  The database user password will be encrypted so its expected that someone within your organization should know the password for the given database user
  6. change the Alias value, we suggest adding the text "(oledb)" to the end
  7. close the Configure Database Manager screen
  8. click the Add button on the Database Managers tab, this should display the Add Database Manager (Native) screen
  9. enter the Alias value to be that of the original database manager
  10. enter the database details that were noted a couple steps ago
  11. click the Test button to confirm that a connection can be made
  12. click the OK button to save the connection
  13. edit the Database Manager you created in the previous step and adjust all the settings to match those of the original database manager
  14. test your clients can access the repository (using the original Alias)
  15. once everything is confirmed to be working as expected the renamed database manager can be deleted

Migrating ODBC based connections

An OLE/DB connection string should contain all the necessary details, therefore the migration process consist of the following steps:

  1. open the Sparx Systems Pro Cloud Server Configuration Client
  2. select the ODBC based Database Manager within the list
  3. click the Edit button, to review the connection details of the Database Manager
  4. make a note of all settings on the Configure Database Manager screen, as well as the extended ones for Run Scheduled Chart Generation and Periodically Generate Diagram Images for WebEA & Prolaborate
  5. make a note of ODBC DSN
  6. open the ODBC Data Source Administration screen, locate the ODBC DSN and click Configure
  7. make a note of all database settings saved within the DSN. ie Server Name, Port, Database Name and User.  The database user password will be hidden so its expected that someone within your organization should know the password for the given database user
  8. change the Alias value, we suggest adding the text "(odbc)" to the end, this will rename the original database manager to something else
  9. close the Configure Database Manager screen
  10. click the Add button on the Database Managers tab, this should display the Add Database Manager (Native) screen
  11. enter the Alias value to be that of the original database manager
  12. enter the database details that were noted a couple steps ago
  13. click the Test button to confirm that a connection can be made
  14. click the OK button to save the connection
  15. edit the Database Manager you created in the previous step and adjust all the settings to match those of the original database manager
  16. test your clients can access the repository (using the original Alias)
  17. once everything is confirmed to be working as expected the renamed database manager can be deleted

Learn more