Comparing Source and Target Definitions

This chapter includes an overview and discusses how to:

• Work with compare reports.

• Work with workspace reports.

• Work with browser reports.

• Work with composite reports.

• Work with definition status.

• Compare and merge page definitions.

• Compare definitions for upgrade using the command line.

Understanding the Compare Process

PeopleSoft Application Designer enables you to compare the contents of the database to which you are signed on (or project within) with the target database or an exported project file. It enables you to view the status of each definition in each location so you can then decide which definitions to keep.

There are two ways to compare definitions:

• Compare all database definitions of a certain type, such as record definitions. After doing so, you populate the upgrade project with only the definitions that are defined differently in the source than in the target.

• Compare only the definitions in the current upgrade project to the equivalent definitions in the target database or file.

When performing comparisons between source and target definitions, PeopleSoft Application Designer enables you to:

• Generate workspace reports.

  These reports appear in the PeopleSoft Application Designer workspace immediately after the compare process completes.

• Generate browser reports.

  These reports are written to HTML and XML files enabling you to open the report in a browser, share the report with coworkers easily, and store report data in an industry-standard format.

• Visually compare page definitions.

  This feature enables you to view the source and target page definitions side-by-side with differences clearly marked.

• Visually compare and merge text definitions.

  This feature enables you to view the source and target PeopleCode, HTML, SQL, XSLT definitions side-by-side with differences clearly marked. It also enables you to merge source PeopleCode with target PeopleCode.

Comparing All Definitions by Type

PeopleSoft Application Designer performs comparisons on one definition type at a time. For each definition type that you select, the system removes any existing definitions of that type from the current project and repopulates the project based on the comparison results. For this reason, be careful when performing a database comparison on a predefined project.

For example, suppose that your project includes several record, page, and menu definitions and you perform a database comparison on pages only. All of the page definitions that were originally in the project are removed and replaced by any page definitions that were found in the Compare process. However, the record and menu definitions in the project are not affected.

Performing a database comparison overwrites custom upgrade settings with the defaults for the specified target orientation.

Comparing Definitions by Project

If you manually inserted definitions into the project and you want to see how those definitions differ from the same definitions in another database, perform a project comparison. This method compares only the definitions in the project and does not repopulate the project—except in record and field comparisons. Upgrade settings are never modified when you perform a project comparison.

When records are compared—during a database or project comparison—differences that are found in record fields are written into the project. For example, suppose that Record A in the source database contains record fields 1, 2, 3, 4, and 5, and Record A in the target database contains fields 2, 4, 6, and 7. Before the comparison, the project contains only Record A. After the comparison, the project contains Record A and record fields 1, 3, 5, 6, and 7.

Similarly, when field definitions are compared, differences that are found in the field labels are inserted into the project as new field definitions. For example, suppose that you are comparing the source with the target, and both databases have the same field definitions. However, the field label for one of those field definitions is different. The source field definition is labeled Employee ID, but in the target, it is labeled Staff ID. The Compare process creates a new field definition that is labeled Staff ID. After the comparison, the project contains both an Employee ID field and a Staff ID field.

Note. These are the only situations where a project comparison repopulates a project.

Synchronizing Databases When Comparing Record Definitions

The Upgrade Copy process synchronizes databases when performing an upgrade compare and copy for record definitions. During the upgrade copy (CopyProp only) of a table, subrecord, or temporary table, the system reorders the indexes (_, 0 through 9) to follow the source index order. The target order matches the source order after the copy.

For example, suppose that the source record, Z, is a table with fields B, A, C, G, H and the target record, Z, is a table with fields A, B, F, G, C, H where all of these conditions are true:

• F is a customization and a Key field.

• A and B are exactly the same except for field order, and both are keys.

• C, G, H are exactly the same except for field order, and they are nonkey fields.

In this example, the upgrade compare produces project items for this record:

* Unless the F record field is deleted, an upgrade copy and compare always shows this project item.

The result of an upgrade copy on this record changes record fields A, B, F, G, C, and H in the target database to B, F, A, G, C, and H, without moving the nonkey fields. Another upgrade compare would produce the same project items.

Likewise, during an upgrade copy of a view or dynamic view, the target order is reordered to match the source when a record field project item is copied and the source order does not match the target order.

For example, suppose that the source record, Z, is a view with fields B, A, C, and the target record, Z, is a view with fields A, B, F, C where all of these conditions are true:

• F is a customization.

• A and B are exactly the same except for field order.

In this example, the upgrade compare produces project items for these record fields:

* Unless record field F is deleted, an upgrade copy and compare always shows this project item.

The result of an upgrade copy changes A, B, F, C in the target database to B, F, A, C.

Another project compare would produce these project items:

* Unless F is deleted, an upgrade copy and compare always shows this project item.

Working With Compare Reports

This section discusses how to:

• Run a compare report.

• Work with the Compare and Report dialog box.

Running a Compare Report

To perform a comparison:

1. Save any changes to objects and close all windows before starting the Compare process.

   This ensures that all generated reports are saved during the Compare process. Once the process is complete, you can open the reports from a file and view them online.

2. Lock all of the PeopleSoft Application Designer definitions in the target database.

   If you perform a full comparison, it might take several days for you to review all of the comparison reports and set the upgrade settings accordingly. Locking the PeopleSoft Application Designer definitions in the target database ensures that those definitions cannot be changed between the comparison and the time that you perform the copy.

3. Turn off all tracing.

4. Select Tools, Compare and Report, and select one of these options:

   • From Database: The PeopleSoft Signon dialog box appears, prompting you to sign in to an upgrade target database.

   • To File: The Compare and Report From File : Select Project dialog appears for you to select the project to compare.

5. On the Compare and Report dialog box, select the types of definitions to compare from the Definition list.

6. Click Options to access the Upgrade Options dialog box.

   Set all upgrade options including comparison report filters.

7. Select the appropriate Project Item Status / Insert Child Definitions option (if enabled it allows you to preserve the original project).

8. Click Compare to perform the comparison.

   The system creates online reports for the definitions that you are comparing. Upgrade Compare reports are saved to the location you specify in the Report Output Directory field in Tools, Options on the General tab.

Note. You can also compare definitions using command line syntax.

Working with the Compare and Report Dialog Box

Access the Compare and Report dialog box.

Note. Depending on whether you are comparing to a database or from a file, the dialog box name changes accordingly.

Working With Workspace Reports

PeopleSoft provides online comparison reports in PeopleSoft Application Designer. These reports appear in the project workspace area after you run a compare report.

This section discusses how to:

• Access reports.

• Search for definitions in reports.

• Print the report.

• Save reports as text files.

Accessing Reports

To access reports:

1. Select Tools, Compare and Report from the PeopleSoft Application Designer toolbar.

2. Sign in to the target database.

   The system automatically displays a comparison report for each definition that you selected to be copied. If the current definition type has a PeopleSoft Application Designer based editor, you can double-click the definition name in the report to open it. If the comparison report is large, you can search for specific definition names.

Searching for Definitions in Reports

For long compare reports, it is useful to perform a search to locate specific items. The Find in Report feature searches by column. To search for an object in a comparison report highlight or place your cursor in the column that you want to search and select Edit, Find in Report.

Printing the Report

This section provides an overview of a report and discusses how to:

• Print the comparison report.

• Print a comparison report from a file.

• Move print files.

Printing the Comparison Report

This is a print preview of the comparison report:

To print the comparison report select File, Print. The standard Print dialog box appears, enabling you to select the printer, number of copies, and so on.

Printing a Comparison Report From a File

To print a comparison report from a file:

1. To print a saved comparison report, select File, Report from File.

2. Select Print Preview, Print, or View Report.

   These options require that you specify the report name and its location in a standard Open dialog box. View Reportdisplays the specified report in the project workspace.

Moving Print Files

You might want to move the comparison report files to another directory or send them as email attachments. Each comparison report file is saved as two files with the following format:

• Upg<number>DefinitionType.prt

• Upg<number>DefinitionType.idx

Both files (filename.prt and filename.idx) are required to view or print the report.

Saving Reports as Text Files

While the report is open in the workspace, you can save the workspace report as a text file. This enables you to import the report results into applications of your choice, such as Microsoft Excel.

To save the workspace report as a text file:

1. Select File, Save Report As.

2. On the Save Report As dialog box insert a file name into the File Name edit box, and select a file type from the Save as type drop-down list.

   You can select Tab Delimited (.txt) or Comma Delimited (.csv).

3. Click Save.

Working with Browser Reports

This section provides an overview and discuses how to:

• Access and share browser reports.

• Select a project.

• Search for definitions.

• View report details.

• View status summary.

• View compare results by definition type.

Understanding Browser Reports

Browser reports enable you to view compare results using your browser.

You use the Compare Report Viewer to view and navigate within the results. The Compare Report Viewer is a client-based HTML program through which you view the compare results, which are stored in XML. Having the compare results in HTML and XML enables you to:

• Share compare results online with colleagues that do not have PeopleTools installed.

• Display results in custom formats using the data stored in the generated XML files.

By setting the Generate Browser Reports option, when you run the Compare and Report process, the system generates browser reports in addition to the workspace reports that automatically appear in the PeopleSoft Application Designer workspace.

Accessing and Sharing Browser Reports

This section discusses how to:

• Access browser reports.

• Share browser reports.

Accessing Browser Reports

To access a browser report double-click on the line in the output window containing "Browser Compare Report Created.”

The Viewer menu contains menu options related to navigating within the report. The Definition Types menu enables you to dill down into the compare data for each definition type compared. The Definition Types menu only contains the definitions compared.

Sharing Browser Reports

PeopleSoft Application Designer writes the browser reports to a subdirectory named after the project name within the Report Output Directory specified on the General tab on the Options dialog. For example, if the Report Output Directory is c:\psreports and the project name is “PROJECT,” then the browser reports exist in c:\psreports\PROJECT. To view the compare results, double-click CompareViewer.html and then select the desired project name.

For each type of definition you compare, there is a subdirectory containing XML files storing the compare data for that definition type. For example, if you compared pages, the XML file containing compare data for the page compare exists in c:\psreports\PROJECT\Pages. These files can be used as source data for custom displays of the compare data. The PeopleSoft Compare Report Viewer uses these XML files along with various HTML and XSL files to present your compare data.

To share the browser reports, PeopleSoft recommends:

• Copying the entire high-level report output directory (containing all subdirectories, HTML, and XSL files) and copying it to a shared network drive.

• Compressing the entire directory and sending or posting individual copies as needed.

Selecting a Project

If you've run multiple compare reports on the same workstation, the PeopleSoft Compare Report Viewer enables you to switch between them easily.

To select a project:

1. Click Select Project.

2. Select the appropriate project in the Project Name list.

Searching for Definitions

You can search for specific definitions within the compare data.

To search for definitions:

1. Select Search.

2. From the Definition Type list, specify the appropriate definition type, such as Records.

3. In the Search Text edit box, enter the name or part the name of the definition you want to view.

   Note. You must enter at least three characters.

   Note. The search returns the parent and child definitions. For example, if you enter 'RecordA' that contains FieldB and Field C, the search returns RecordA, RecordA.FieldB, and RecordA.FieldC. Also, the search returns all definitions beginning with the search string entered.

4. Click Search.

Viewing Report Details

Click Report Details to view information related to the databases and/or files compared.

Viewing Status Summary

To view the status summary, click Status Summary.

The status summary is a high-level view of the compare results showing the definitions compared and the occurrence of differences. The summary table indicates whether the difference occurred because of additions, modifications, or deletions that were the result of activity at your site, or whether the difference occurred as a result of an addition or modification made by PeopleSoft. This summary can be useful for managers and executives who are scoping and budgeting for an upgrade.

Each of the columns in the status summary indicate the number of items found to differ by definition type. The columns represent the "Source" and "Target" status values set during the compare process. You can click on any of the cell values to view the items filtered for each particular status result. You can also click the value in the Definition Type column to view further status information.

The following table shows how each column in the status summary table equates to the status in the source and target locations.

Note. If you have generated composite reports, two tabs appear for the status summary: Compare Report and Composite Report.

Note. The compare report values reflect the assumption that the source is the delivered PeopleSoft demonstration database and the target is a customer's production copy of a database.

See Also

Working with Definition Status

Viewing Compare Results by Definition Type

The Definition Types menu displays a menu item for each type of definition you compared. Click the link for a particular definition type to view the comparison results for each definition of that type.

Each definition compared appears in a grid containing identification information relevant to that definition type as well as the status of the definition in each location, the action, and the upgrade flag. The identification columns are links enabling you to drill down into the compare results of that definition so you can compare source and target values.

Note. If you have generated a composite report, two tabs appear: Compare Report and Composite Report.

See Working with Definition Status.

Working with Composite Reports

This section provides an overview and discusses how to:

• Generate composite reports.

• Work with composite report output.

• Example: Create a composite report.

Understanding Composite Reports

When performing a PeopleSoft application upgrade, part of the process involves identifying the customizations made on your previous database and ensuring that all customizations are reflected in the upgraded database. During the development of a new PeopleSoft application release, many changes are made to the underlying meta data of the PeopleSoft application. If your application database is highly customized, it's likely that you've customized at least some of the definitions that PeopleSoft has modified in the new release. You identify your customizations and PeopleSoft modifications by running compare reports.

For example, suppose you are performing an upgrade from PeopleSoft 8.1x applications to PeopleSoft 8.4x applications. To identify your customizations, you run compare reports between your current 8.1x production database and the delivered 8.1x DEMO database. Then, to view your customizations and the PeopleSoft modifications after your 8.1x database has been upgraded to the 8.4x version, you run compare reports between your upgraded database and the delivered DEMO version of the 8.4x database.

Generating composite reports during this process greatly enhances your ability to identify the definitions that both you have customized and that PeopleSoft has modified. Composite reports compare your previous compare reports to the target database. The information in the previous compare reports is considered a subset of the composite reports. That is, all data appearing in the previous compare reports also appears on the composite reports, and those attributes that were updated by your organization and PeopleSoft will be highlighted.

The report output displays the changed attributes of the definitions so that you can determine the level and granularity of your customizations and how much effort will be involved in reapplying your customizations during the upgrade. This information can assist the decision making process when assessing the upgrade project scope.

Note. Composite reports are not a comprehensive record of all changes in the system. They only reflect definitions that have been changed by PeopleSoft and by a customer implementation.

Note. Composite reports do not replace compare reports. Rather, a composite report provides an alternate display of the information in compare reports, showing information appearing in both old release and new release compare reports.

Note. Composite reports are generated only for definitions that exist within both databases. For example, Analytic Model definitions used for the PeopleSoft Analytic Calculation Engine do not exist in a PeopleTools 8.1x application database. If comparing between a PeopleTools 8.1x application database and a PeopleTools 8.47 application database, a composite report for Analytic Model definitions will not be generated, as those definitions do not exist within a PeopleTools 8.1x database.

Generating Composite Reports

Before generating composite reports, consider the following:

• Compare report output (.PRT files and .IDX files) generated from the previous version must exist in an accessible directory. All reports must exist in the same directory, and the report file names must not have changed since they were originally generated.

• The previous compare reports must have been generated on applications running on at least PeopleTools 8.1x. Compare reports generated by PeopleTools versions prior to 8.1x, such as PeopleTools 7.x or 7.5x are not supported.

• Composite reports should only be generated when necessary, as in during the Enterprise upgrade process. Generating composite reports can be time consuming and can cause performance degradation.

• If you have selected Generate Browser Reports on the Report Options tab in the Upgrade Options dialog box, the system also generates browser reports for the composite reports. To view the composite reports in the browser, click the Composite Report tab in the Report Viewer.

• Any filtering options you've set on the Report Filter tab in the Upgrade Options dialog box also apply to the composite reports.

To generate a composite report:

1. Make sure that the compare reports generated from your previous release exist and reside in an accessible directory.

2. Launch Application Designer and sign on to the delivered PeopleSoft demonstration database.

3. Select Tools, Compare and Report, To Database.

4. On the Compare and Report dialog box, select Options.

5. On the Upgrade Options dialog box, select the Report Options tab.

6. Select the Generate Composite Reports check box, which activates the Old Release Report Output Directory and Old Release Source Database Name edit boxes.

7. In the Old Release Report Output Directory edit box, enter the directory where the compare reports generated from your previous database reside.

8. In the Old Release Source Database Name edit box, enter the name of your original, source database (which is typically the PeopleSoft demonstration database from the previous release), and click OK.

   At this point, the process is identical to running a typical compare report. When the report completes, Application Designer displays both reports: the regular compare report and the composite report for each type of definition compared.

Note. The naming convention for composite reports is similar to compare reports, only the prefix for composite report file names is "Cmp". For example, the naming convention for composite reports is Cmp<number><definition>, as in Cmp05Pages.prt and Cmp05Pages.idx.

Working With Composite Report Output

Generate a composite report.

Old Release	Previous release source data value. In a PeopleSoft upgrade, this is the source value from the DEMO database in the previous release.
New Release	New release source data value. In a PeopleSoft upgrade, this is the source value from the DEMO database in the new release, which reflects the modification performed by PeopleSoft development teams. If no modification has been made by PeopleSoft for a particular attribute, the value "<same>" appears in the New Release column. Note. Changes represented here are not necessarily performed by PeopleSoft. If the compare reports were ran against your development environment, the modification was made in-house, not by PeopleSoft.
Customization	New release's copy of the production target value. In a PeopleSoft upgrade, this is the target value from the copy of the production database against which all upgrade scripts have been run.

Example: Creating a Composite Report

To illustrate how the system compiles and displays composite report information, this section provides a simple example. Keep in mind that this example only displays information for one definition. A typical composite report can contain information pertaining to hundreds of definitions. This example shows:

• Compare report results between a PeopleSoft 8.1 demonstration database and PeopleSoft 8.1 production copy.

• Compare report results between a PeopleSoft 8.4 demonstration database and PeopleSoft 8.4 production copy.

• Composite report result based on the previous compare report results.

Compare Report Results Between a PeopleSoft 8.1 Demonstration Database and PeopleSoft 8.1 Customer Production Database

This compare report shows customizations. For the field, FLD1, the following customizations were made:

• Field Length: 10 to 12

• Description: ABC to XYZ

• Owner ID: PPT to CUST

With these customizations, the compare report results would appear as follows:

Compare Report Results Between a PeopleSoft 8.4 Demonstration Database and PeopleSoft 8.4 Customer Production Database

This report shows customizations and PeopleSoft modifications.

For the field, FLD1, the following customizations were made:

• Field Length: 10 to 12

• Description: ABC to XYZ

• Owner ID: PPT to CUST

For the field, FLD1, PeopleSoft made the following modifications:

• Field Length: 10 to 14

• Format: Upper to Mixed

• Field Type: Char to Long Char

With these customizations, the compare report results would appear as follows:

Composite Report Result Based on the Previous Compare Report Results

The following table is a sample composite report only showing the attributes from the previous compare reports that were changed by both PeopleSoft and a customer.

Working with Definition Status

This section discusses how to:

• Determine definition status.

• Compare source status to target status.

Determining Definition Status

PeopleSoft Application Designer defines the status of a definition in the source and the target database.

Note. Compare by release date is determined by finding the highest release label in common between the source and target databases. PSRELASE.RELEASELABEL column is searched on both source and target to find the latest common value between the two. Then PSRELEASE.PSRELEASEDTTM for that label is used for compare by release date for the source and target, respectively. You can override this value to set a different release label, or specific compare by date, on the Upgrade Options interface. Only common release labels (found on both source and target PSRELEASE table) can be used.

Comparing Source Status to Target Status

The following table summarizes the possible status, action, and upgrade values that could be applied to a single definition during the comparison process.

The Action, Other Action, PeopleSoft Vanilla, and Keep Customizations are described in the following sections.

Action

Describes the upgrade action set for an item.

Other Action

Describes the action when the system finds differences in record or field definitions.

Note. Used for record and field definitions only.

PeopleSoft Vanilla

Describes the setting of the Upgrade flag for the project item when performing the Vanilla Compare type (set on Upgrade Options).

Keep Customization

Describes the setting of the Upgrade flag for the project item when performing the Keep Customizations Compare type (set on Upgrade Options).

Comparing and Merging Page Definitions

This section discusses how to:

• Compare and merge page definitions.

• Work with the Diff / Merge Page interface.

Comparing and Merging Page Definitions

To compare and merge page definitions in the Upgrade view:

1. Open the upgrade project, and make sure that you are in the Upgrade view.

2. Open the Pages window within the upgrade project.

3. Select the page(s) that you want to compare.

4. Right-click on the Pages window to display the context menu.

5. Select Diff / Merge Page, and then select one of these options:

   • From Database: select if you are comparing the current definitions with definitions in another database. After doing so, sign on to the appropriate database using the PeopleSoft Signon window.

   • From File: select if you are comparing the current definitions with definitions in a project file. After doing so, navigate to the appropriate file using the Merge from File: Select Project dialog box.

To compare and merge page definitions from the Development view:

1. Open the page definition that you want to compare.

2. Select Diff / Merge Page, and then select one of these options:

   • From Database: select if you are comparing the current definitions with definitions in another database. After doing so, sign on to the appropriate database using the PeopleSoft Signon window.

   • From File: select if you are comparing the current definitions with definitions in a project file. After doing so, navigate to the appropriate file using the Merge from File: Select Project dialog box.

Note. For the compare to work, the name of the page in the external database or project file must have the same name (the same key value) as the page in the current database.

Working with the Page Compare Results

This section discusses how to:

• Use the Diff / Merge for Page interface.

• Determine differences between page definitions.

• Use the Properties panel.

• Merge attributes and properties from source to target.

Using the Diff / Merge for Pages Interface

After successfully connecting to the database or file, the interface appears similar to the following example.

The PeopleSoft Application Designer displays a Property Value panel to show details about every difference or each changed page control. To the right, each page is displayed side-by-side enabling the visual comparison.

Note. The pages appear in a read-only state. You cannot make any changes to either page definition from the Visual Compare interface.

Determining Differences between Page Definitions

When there are differences between source and target page definitions, the system illustrates this in the Layout tab by surrounding the page field with a red box with a red 'X' at the top, left-hand corner. The field in which you have placed your cursor has a dotted line surrounding it.

On the Order tab, page controls that have differences are highlighted in red. Also, if you select a page control, you can see easily if its order is different as the highlighted areas do not match.

Use the Previous Difference and Next Difference toolbar buttons to navigate quickly between the differences flagged within the active window.

Using the Properties Panel

The Properties panel enables you to view the details regarding the differences between the source and target page controls. You can move the panel and dock it to the desired locations.

By placing your cursor into each page control surrounded by a red box, the differences in properties between the source and target definition for that particular page control appear on the Properties panel. You can also use the TAB key to move from field to field. For page controls that are identical between the source and target, nothing appears in the Properties panel.

Page fields are identified in the Property Value panel by the field ID value displayed on the Order tab.

Property	Displays the list of properties associated with a particular page field or control. Note. The properties appearing for different page fields and controls may differ. Many of the properties are only used internally by PeopleTools for page display and position.
[A] <Signed on Database Name>	Displays the property values for a page field or control residing in the database to which you are currently signed on. In the context of merging pages, this is the "target" definition.
[B] <Database Name/Project File Name>	Displays the property values for a page field or control residing in an external database or project file. In the context of merging pages, this is the "source" definition.

Note. If needed you can access the page definition properties by selecting File, Object Properties or clicking ALT + ENTER.

Merging Attributes and Properties from Source to Target

When merging attributes of a page definition it is important to keep in mind where the two definitions you are merging reside. The database to which you are signed on is A:, or the "target," and the database or project file from which you are merging page properties is B:, or the "source."

Use the A and B buttons to control the merging of page definitions between the target and source.

Using the Merge Output Window

After running a diff / merge for pages operation, the Merge tab appears in the output window of the Application Designer work space. The Merge tab enables you to view the status of your merge operation as it records each event, such as:

• the initiation of the merge.

• the name of the page being compared.

• the number of differences identified between the two definitions.

• the operations that have occurred (merge Add, undo merge, and so on).

• the name of the saved, merged page definition.

For example:

Opening Visual Merge: MYPAGE(Page)

Comparing [A(ENG,DUT)], [B(ENG,DUT)]

2 difference(s)

(5) Merge: [B](ID:5)–>[A](ID:5)

(4) Merge, Add: [B](ID:13)–>[A](ID:0)

Save [A]:MYPAGE_NEW(Page)

Saving Merged Definitions

After you have determined that all of the appropriate page fields and page controls have been merged into your target definition, save your changes. By doing so, the system renames the target definition according to the following naming convention:

<previous_page_name>_NEW

Comparing Definitions for Upgrade Using the Command Line

Use the same command line syntax as identified previously to compare definitions.

See Understanding PeopleSoft Application Designer Command Line Parameters.

Use the command line statement for an Upgrade Compare process to:

• Connect to the source database.

• Connect to the target database.

• Perform a project or database compare (based on parameters).

• Create compare reports in the specified output directory.

Available Parameters

This table lists all of the available parameters for the upgrade compare statement:

-FLTR XXXXX XXXXX XXXXX
 XXXXX XXXXX

-FLTR 00000 00011 00011
 01111 01111

Example: Running an Upgrade Compare Process

Use this example as a guide for running an Upgrade Compare process:

• Run a database Compare process against the source Microsoft SQL Server database, PTDMO, and the target database, PTTST.

• Log process and error messages to c:\temp\compare.log.

• Set the commit limit to 150.

• Show the audit flag and DDL differences between databases.

• Compare records, indexes, pages, queries, and process definitions.

• Compare only English and Spanish translations.

• Set the database compare type.

• Set the target orientation to keep the customizations.

• Compare by release 8.40.00.000.

• Generate compare reports to the c:\temp\upgreports directory.

PSIDE.EXE −HIDE -CT MICROSFT -CD PTDMO -CO PTDMO -CP PTDMO -PJM PPLTOOLS -TD PTTST -TO PTDMO -TP PTDMO -QUIET -LF C:\TEMP\COMPARE.LOG -CL 150 -AF 0 -DDL 0 -OBJ 0,1,5,10,20 -LNG ENG, ESP -CMT 0 -TGT 1 -CBY REL Core 8.40.00.000 -ROD C:\TEMP\UPGREPORTS