Script Analysis tab
The Script Analysis tab is automatically populated with you scan design scripts (see Scan Design Scripts).
This tab contains the following:
Table 28. Script Analysis tab
Allows you to run the script scan again by clicking Script Scan.
Allows you to add or remove database objects.
Design Analysis tab
This tab contains the following:
Table 29. Design Analysis tab
• Forms: Number of forms used in the database
• Views/Folders: Number of views/folders used in the database
• Agents: Number of agents used
• Total: Total number of design elements
• Design Details button opens the Design Element Details dialog boxFrom the Design Element Details dialog box (click Design Details), you can view the design elements of the database organized by type.
To exclude particular design elements from the Complexity tab calculations, highlight the elements in the dialog box and click Exclude. The elements that have been flagged for exclusion will have a red ‘X’ next to them. To re-include an element, select it and click the Exclude button again. An example for needing to exclude elements is if you know you are not going to be migrating any web only design elements. Then you don’t want them part of the design complexity analysis so you would filter out all the web-only design elements. Use the Quick Filter as a quick way to Exclude multiple elements. You will need to rerun the Recompute database details for the design analysis to be updated for the database.
You can also select a Notes Form that you want migrated to an InfoPath or Nintex form template. Select the Form you want migrated and click the Export to InfoPath Template button, or right-click and from the context menu select the menu item Export to InfoPath form template.
For detailed information on this process, see Generate InfoPath form template.
This is where you can measure deviations in design between the current database and another database (typically a design template or another database that you suspect is based on a common design). Identifying similar databases can be very useful when planning your migration process. To select a template or similar database to compare to, check the box and click the Select button. The Default button will automatically find the template database based on the template name, if there is one. You can assign the reference database automatically during the Auto Triage process by setting up a Class Rule and using the fields on the Auto Triage tab.
• Design Element Delta: Difference in design between the current database and the reference.
• Percent Match: Percentage the database matches the reference
• Difference Details: To see the detailed differences, click this button.The Class Template Match Details dialog shows all the partial matches as well as the best fit match. To associate the technical class of one of the matches to the current database, highlight the class name and click Set as Technical Class for Database.
• Best Fit: The technical class template that best matches the database in regards to design.NOTE: For a technical class template to be considered in the Best Fit analysis, it’s property, Include in “Best Fit” testing for all databases, must be checked in the Class Template Tab of the Technical Class Properties sheet. For a quick way to include all the Notes databases and templates that you want as technical class templates for Best Fit analysis, use the Create Technical Class database action.
• Percent Match: Percentage the database’s design matches the best fit class template’s design.
• Details: To see the class template match details, click this button.
Complexity tab
Once a design scan and/or data scan is completed, a summary of data patterns in use are displayed in this tab. The global complexity settings from the Global Option’s Analysis tab are used in the complexity computations in this tab.
This tab contains the following:
Table 30. Design Analysis tab
If the Microsoft Design Element Index is defined as a factor to use in the automatic complexity assignment as defined in the Analysis tab of the Global Options, then this section will be filled out using the published DEI algorithm.
• Average: Average number of the Index
• Max: Maximum number of the Index
• Calculations: This button will open a dialog box that shows the detail calculations of the IndexThis information is populated when the Scan Data is run.
• Computation: Overall data complexity recommendation of the database using the algorithms defined in the Analysis tab of the Global Options.
• Details: To view the data details click this button. This will take you to the Data Analysis tab which shows a summary of similar data record counts summarized by Form Used.
• Data Scan: This button runs the data scan against the database to populate the Data Complexity. This process can also be run from the database actions list in the database context menu. For more information, see Scan Design ElementsThis information is populated when the Scan Design is run.
• Computation: Overall design complexity recommendation of the database using the algorithms defined in the Analysis tab of the Global Options.
• Details: To view the design details click this button. This will take you to the Design Analysis tab which shows a list of all interesting design elements in the database with basic information about each.
• Design Scan: This button runs the design scan against the database to populate the Design Complexity. This process can also be run from the database actions list in the database context menu. For more information, see Scan Design Elements
• This number will be automatically computed and filled in when the Design and Data Scans are run. A weighted average of the algorithms will be used, depending on the preferences you set in Advanced configuration options. You should always treat automatic calculation as an approximate indicator of complexity and perform a detailed analysis of databases before performing the actual migration.
Migration Effort tab
Databases that qualify to be members of the given class can have their migration effort automatically set using the information defined in this tab. To do this, you must run the Apply class rules action for the databases once this tab is filled out.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Conditions d’utilisation Confidentialité Cookie Preference Center