Horizons Manufacturing Suite for Select/ Professional 7.0 Database Migration Instructions
Copyright Copyright 2002-2003 Horizons International, Inc. All rights reserved. Information in this document is subject to change without notice. The software described in this document is furnished under a license agreement or nondisclosure agreement. The software may be used or copied only in accordance with the terms of those agreements. No part of this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means without the prior written permission of Horizons International, Inc. Horizons International, Inc. 5520 Wellesley St., Suite 200 La Mesa, CA 91942 U.S.A. www.hzs.com Version 7.70, Revision 1
Table of Contents Changing Database Platforms...6 LOADING THE CHUNK FILE...6 Migrating CTree to PSQL...7 Migrating to MSSQL...9 4
5
Changing Database Platforms Database Migration Instructions This portion of the document is only to be used when converting from one database platform to another. For instance, if you are currently running a CTree or Pervasive SQL database and you want to convert to a Microsoft SQL or MSDE database. You must contact Horizons International to receive the Migration Tool. Please call 1-800-287-8014 for information. NOTE:BEFORE YOU BEGIN MAKE SURE YOU HAVE ENOUGH DISK SPACE ON THE DRIVE THE DATA WILL BE EXPORTED TO, IN ORDER ACCOMMODATE ALL OF THE DATA TABLES. This program supports two methods of migration depending on the database that you are migrating to Import to PSQL from Ctree or export to MSSQL or MSDE from Ctree, Faircom or PSQL. It also possible, if desired, to export the data from PSQL or MSSQL/MSDE to Ctree tables. When migrating to MSSQL or MSDE the migration tool will use the ODBC setup for SQL to transfer the data directly to MSSQL/MSDE. This is accomplished by marking the Migrate to MSSQL checkbox on the Export Tables window. Installation Make sure the latest Horizon s code matches the Select/Professional version on both sides, i.e. old database and new. If replacing Migration Tool code, make a backup copy of the HZ_MT.DIC file in case the new code is not correct. Also verify that you have the correct Migration version for the version of Horizons. Copying The Install File To The Select/Professional Directory: The HZ_MT.CNK file will be installed into the Select/Professional root directory of the station that you are migrating from, except when migrating from Ctree to PSQL, in which case you will be importing from the PSQL side. To install the chunk file copy the HZ_Mig.exe or HZ_Mig.cnk file to the Select/Professional directory. In a File Manager, double click to unpack the exe file (this is not necessary if using the.cnk file). This file can also be unpacked at the Command Prompt level by typing the file name when in the Select/Professional directory. Make sure the file attribute is NOT read only. (Right click on the file and choose properties) LOADING THE CHUNK FILE When Select/Professional is started a message will appear asking to include the new code. Answer Yes. Upon loading, a dictionary will be created called HZ_MT.DIC and entries will be made into the Dynamics.set file showing the product ID of 2086 and the paths to the dictionary (:C:Dynamics/HZ_MT.DIC) the reports dictionary (:C:Dynamics/HZMTRPTS.DIC) and the forms modifications dictionary (:C:Dynamics/ HZMTFRMS.DIC). 6
Database Migration Instructions ADDING THE PROGRAM TO THE SHORTCUT BAR - Select/Professional 6.0+ Enable the Shortcut Bar by selecting the toggle switch Shortcuts icon at the top of the screen. Next move your mouse pointer to the left edge of the screen to expose the Shortcut Bar. Select Add Other Window Horizons Migration Tool Inventory HZ_MT_Palette Add Done. USING THE MIGRATION TOOL This program supports two methods of migration depending on the database that you are migrating to. Migrating CTree to PSQL If exporting from the Faircom database you can only migrate to MSSQL/ MSDE (see the next section). 1. Upgrade your Ctree version to the requirements noted at the beginning of this document. 2. Create a Select/Professional PSQL installation of the same version as the Ctree installation. a. Install the Horizons Manufacturing product, either using the Install wizard or by manually copying the.cnk file, into the root directory of the PSQL installation of Select/Professional. Note that this must be the same version that is installed in the Ctree version. 3. Load the Migration Tool chunk file in the PSQL root directory, start Select/ Professional 4. Log in. 5. Include the new code. Add the Migration palette to the shortcut bar (see above). 6. Open the Migration Registration window from the Migration palette. 7. Enter Registration Keys. 8. Run the Horizons Product File Maintenance in the Ctree version. 7
Database Migration Instructions 9. Open the Import Tables window in the PSQL version of Select/ Professional. 10. Select a product in the Product drop down menu. 11. If you are migrating Horizons Manufacturing Suite (the Manufacturing Suite option in the Product drop down) or Configurator, select a build number in the Build drop down menu. For Configurator, also enter the Select/Professional version in the S/PVersion field. 12. Select the Import Path by clicking the yellow folder. THE IMPORT PATH MUST BE SET TO THE DIRECTORY YOU WANT TO IMPORT YOUR TABLES FROM. The path that defaults is the Inventory directory of the company you are logged into. Select the path where the Ctree data is found. The data for Horizons Manufacturing Suite is kept in the Inventry directory and all tables start with BOM. The data for Item Pricing Matrix is kept in the Inventry directory and all tables start with IP. The data for Horizons Contact Manager is kept in the Sales directory and all tables start with HCM. The data for Configurator is kept in the Inventry directory and all tables start with CFG. The Path that is created will be written to the Pathnames table in Select/ Professional. You can see it also in the Pathnames window (File Maintenance Pathnames) under the Inventory/Sales series Migration, and Prod- 8
Database Migration Instructions Migrating to MSSQL or MSDE NOTE: The Migration Tool will not error if the tables are missing. Confirm that the tables are created by using the Enterprise Manager (the tables all start with BOM...), or go to HMS Setup and confirm that the window opens without any table errors. uct Horizons Migration Tool. THE OTHER PATHS ARE FOR THE HORIZONS TABLES. THEY MUST BE EMPTY OR THE SAME AS THE PATHNAMES FOR THE HORIZONS PRODUCT. If there is a problem saving the path, enter it under File Maintenance Pathnames. Select the Horizons Migration Tool product and the Inventory series. Select the path and mark to update Individual Table. The Table to update will be at the bottom of the list called Migration. Highlight this and then click Apply. Make sure that only that the Migration Table was updated. If any other Tables were updated then they must be set to the path where the Inventory tables reside. 13. After the path is selected a message will appear saying that you must restart Select/Professional for the path change to take effect. Restart Select/ Professional, then continue with the processing of the data. 14. Click the All button to insert all of the tables listed in the Source Tables field into the Destination Tables field. If you want to view the table list on the left by individual table, click on the Show visual switch at the top right of the window until it shows Physical. You can then select individual tables to import. 15. Click the Process button to perform the Import. 16. The progress indicators will show how much of each table is processed and how many tables have been completed. 1. Upgrade the Ctree/PSQL version of your Horizons data to whichever Horizons Build you will be using. For example, build 70. 2. Create a Select/Professional MSSQL or MSDE installation of the same version as the Ctree installation. a. Install the Horizons product, either using the Install wizard or by manually copying the.cnk file, into the root directory of the MSSQL/ MSDE installation of Select/Professional. Note that this must be the same version that is installed in the Ctree/PSQL version. b. Start Select/Professional and log in as the sa (System Administrator) user. c. The necessary tables will be created at this time for HMS. Refer to the installation documentation on how to create tables for the other products. 3. Load the Migration Tool chunk file in the Ctree/PSQL root directory. 4. Start Select/Professional. 5. Include the new code. Add the Migration palette to the shortcut bar (see above). 6. Open the Migration Registration window from the Migration palette. Enter Registration Keys. 7. Run the Horizons product File Maintenance in Ctree/PSQL. 9
Database Migration Instructions 8. Open the Export Data window in the Ctree/PSQL application. 9. Select a product in the Product drop down menu. 10. If you are migrating Horizons Manufacturing Suite (the Manufacturing Suite selection in the Product drop down menu) or Configurator, select a build number in the Build drop down menu. For Configurator, also enter the Select/Professional version in the S/PVersion field. 11. If migrating To MSSQL or MSDE mark the Migrate to MSSQL checkbox. a. Fill in the MSSQL Server name (use the format PCname\DatabaseServerName) and the MSSQL/MSDE Database where data will reside (for example, in the test company The World Online, Inc. the SQL database name is usually TWO). The Horizons SQL tables must already be created. 12. If not migrating to MSSQL or MSDE select an Export Path by clicking the yellow folder. THE EXPORT PATH MUST BE SET TO THE DIRECTORY THAT YOU WANT TO EXPORT YOUR DATA FROM. 13. Click the All button to insert all of the tables listed in the Source Tables field into the Destination Tables field. NOTE:The Logical Files button at the top of the Export Tables window can be clicked to show the individual tables in the Logical File. This allows only the selected tables to be processed. 14. Click the Process button to begin the Migration. When migrating to MSSQL or MSDE you will be asked for the SQL connection and login information. Always log in as sa (System Administrator). 10
Database Migration Instructions 15. The progress indicators will show how much of each table is processed and how many tables have been completed. 11