Application - Config - Update Application schema - KB Update SQL Tool on Documentation - V2

KB Update SQL Tool - CI entry tables

Mon, 01 Jan 0001 00:00:00 +0000

Introduction

As explained in the previous section, in order to modify and update the Analysis schema, a set of entry tables are injected with data that defines how the Analysis schema will be altered.

Entry tables

The following is an exhaustive list of entry tables ordered by function. Each table and its function is described in more detail below.

Error management	CI_ERRORS
Object modification	GUID_OBJECTS CI_OBJECTS CI_NO_OBJECTS
Parent type link modification	CI_PARENTS
Object property modification	CI_STR_PROPERTIES CI_INT_PROPERTIES CI_NO_PROPERTIES
Link modification	CI_NO_LINKS CI_LINKS
Link property modification (available in ≥ 8.3.45)	CI_INT_LINK_PROPERTIES CI_STR_LINK_PROPERTIES CI_NO_LINK_PROPERTIES

CI_ERRORS

This table will be injected with data if any errors or data inconsistencies are found during the data check process (this takes place when the job is executed).

KB Update SQL Tool - Creating OBJECT_GUIDs

Mon, 01 Jan 0001 00:00:00 +0000

Note

Note that in AIP Core ≥ 8.3.45, the table GUID_OBJECTS can no longer be used . Attempting to use it will generate and ERROR_ID = 5 on each returned row. If you have scripts using this table to generate custom OBJECT_GUIDs, for legacy technologies such as VisualBasic and PowerBuilder, you should update those scripts to use the OBJECT_ID (which is always available) instead of generating a custom OBJECT_GUID using this table. In this situation, the information below is obsolete and should not be used.

KB Update SQL Tool - Error handling

Mon, 01 Jan 0001 00:00:00 +0000

The KB Update SQL Tool has a built in error handling system: when a job is launched, a series of data consistency checks are carried out to check that the proposed query will execute correctly. If any problems are detected (for example attempting to insert duplicate OBJECT_GUIDs or attempting to modify a numeric property using the wrong entry table) the job execution will stop. An error ID is then inserted into the ERROR_ID column of the entry table you are updating. You can then query the CI_ERRORS entry table to extract the error information message that will help you debug the problem.

KB Update SQL Tool - Using the KB Update SQL Tool via CAST Management Studio

Mon, 01 Jan 0001 00:00:00 +0000

Info

This documentation is for using the tool in the legacy CAST Management Studio. You should, wherever possible, use Console to run your analyses and the KB Update SQL Tool - see Application - Config - Update Application schema.

Configuring the tool

To configure the tool:

Launch the CAST Management Studio
Connect to the Management Service which governs the Analysis schema you want to modify
Open an existing Application (or create a new one) - note that the Application must use the Analysis Service you want to update - you can check this in the Execute tab of the Application editor: