Analyzer 4.1 MS SQL Server Plug-in Guide

[ LSF Documentation ]

[ Title ]

[ Contents ]

[ Previous ]

[ Next ]

[ Index ]

---

Migrating an LSF Analyzer C-tree Plus Database to MS SQL Server

---

Contents

• Prerequisites
• Step Overview
• Export Data from C-tree Plus to an ASCII File Recognizable by Commercial Database Systems
• Export Data from C-tree Plus to an ASCII File Recognizable by Commercial Database Systems
• Import ASCII Files into the LSF Analyzer Microsoft SQL Server Database

Prerequisites

• You have a version of dm that is 4.0.1 or later
• Microsoft SQL Server is installed

Step Overview

In order to migrate an LSF Analyzer C-tree Plus database to Microsoft SQL Server, perform the following steps:

1. Create the LSF Analyzer database in Microsoft SQL Server.

   Here you create the LSF Analyzer database, create a user login, and import LSF Analyzer database schema tables.

   See Create the LSF Analyzer Database.

2. Export the CTREE Database with dm -ES.

   See Export Data from C-tree Plus to an ASCII File Recognizable by Commercial Database Systems.

3. Import each database table into Microsoft SQL Server.

   For all XXXCode database tables, remap Col001 to XXXCode, Col002 to XXXName.

   See Import ASCII Files into the LSF Analyzer Microsoft SQL Server Database.

Export Data from C-tree Plus to an ASCII File Recognizable by Commercial Database Systems

Use the dm -ES option to export the C-tree database to a format that is recognizable by commercial database systems. Use a 4.1 dm version.

C:\dm -ES target_dir -t ,@ source_dir

Raw data files in Ctree-Plus are in source directory as follows.

For example, if the source directory is c:\raw:

C:\raw
dbLogStatusTable.dat
hostCodeTable.dat
hostConfInfoTable.dat
hostGroupCodeTable.dat
hostGroupTable.dat
hostModelCodeTable.dat
hostStatusCodeTable.dat
hostStatusTable.dat
hostTypeCodeTable.dat
jobExecProcsTable.dat
jobInfoTable.dat
jobResRsvTable.dat
jobRusageTable.dat
jobTypeCodeTable.dat
pendingReasonCodeTable.dat
pendingReasonTable.dat
projectCodeTable.dat
queueCodeTable.dat
resourceCodeTable.dat
resourcesTable.dat
userCodeTable.dat
userGroupCodeTable.dat
userGroupTable.dat

Exported ASCII files are in the target directory as follows. For example, if the target directory is c:\backup:

dbLogStatus.asc
hostCode.asc
hostConfInfo.asc
hostGroup.asc
hostGroupCode.asc
hostModelCode.asc
hostStatus.asc
hostStatusCode.asc
hostTypeCode.asc
jobExecProcs.asc
jobInfo.asc
jobResRsv.asc
jobRusage.asc
jobTypeCode.asc
pendingReason.asc
pendingReasonCode.asc
projectCode.asc
queueCode.asc
resourceCode.asc
resources.asc
userCode.asc
userGroup.asc
userGroupCode.asc

Where to Go Next

Import ASCII Files into the LSF Analyzer Microsoft SQL Server Database

Import ASCII Files into the LSF Analyzer Microsoft SQL Server Database

Import Order

IMPORTANT: Because database constraints exist in the database, import ASCII files in the following order. If you see an error message that the ASCII file size is 0, ignore this and continue the import.

1. hostCode.asc
2. hostGroupCode.asc
3. userCode.asc
4. userGroupCode.asc
5. hostTypeCode.asc
6. hostModelCode.asc
7. queueCode.asc
8. projectCode.asc
9. resourceCode.asc
10. hostStatusCode.asc
11. jobTypeCode.asc
12. pendingReasonCode.asc
13. hostList.asc
14. hostGroup.asc
15. userGroup.asc
16. hostConfInfo.asc
17. hostStatus.asc
18. jobInfo.asc
19. jobResRsv.asc
20. jobRusage.asc
21. resources.asc
22. pendingReason.asc
23. jobExecProcs.asc
24. dbLogStatus.asc

Import ASCII Files into the LSF Analyzer Database

You must manually import each ASCII file into the Microsoft SQL Server.

To import an ASCII file into the LSF Analyzer database:

1. Start | Programs | Microsoft SQL Server | Import and Export Data

   The DTS Wizard window is displayed.

2. Click Next.
3. Choose Data Source.

• Source--Text File
• File Name--ASCII file to import into database

4. Select File Format.

• Delimited
• File type--ANSI
• Row delimiter--{CR}{LF}
• Text qualifier--Double Quote {"}
• Skip rows--0
• First row has column names-- Blank

5. Specify Column Delimiter.

• Comma

6. Choose a Destination.

• Destination--Microsoft OLE DB Provider for SQL Server
• Server--Database Server
• Authentication--Windows or SQL Server (depending on the type of authentication you decided upon when you created your LSF Analyzer Microsoft SQL Server database)
• Database--Select the database you created

7. Select Source Tables.

   For all database tables that end with code, such as hostCode, hostGroupCode, etc., choose Transform. For other database tables, choose Next.

If you selected Transform, you will need to map the Col002 Source to hostName destination and Col001 to hostCode destination.

Your selection should look like the following:

Click Next.

8. Save, Schedule Replicate Package. Select Run Immediately and click Next.

9. Transferring Data. Click Done.

10. Repeat this procedure for all database tables. Tables that do not have a ...Code at the end do not require Columns to be mapped.

[ Top ]

---

[ LSF Documentation ]

[ Title ]

[ Contents ]

[ Previous ]

[ Next ]

[ Index ]

---

Date Modified: February 01, 2001 Platform Computing Corporation: www.platform.com North America: +1 905 948 4297 Europe: +44 1256 370 530 Asia: +86 1062 381125 Toll-Free: 1-877-444-4LSF (+1 877 444 4573) Support: support@platform.com Information Development: doc@platform.com Copyright © 2001 Platform Computing Corporation All rights reserved.