KB Update SQL Tool - Using the tool in specific scenarios on Documentation - V2

KB Update SQL Tool - Removing an existing object using CI_NO_OBJECTS

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

Based on object’s ID

In this example, we are going to remove a VB Sub called “Disconnect” from the Analysis schema. The image below shows the object in CAST Enlighten:

The first step is to insert the data into the CAST entry tables that will cause the object in question to be removed from the Analysis Service when the tool is run:

insert into <KB_name>.dbo.CI_NO_OBJECTS (OBJECT_ID, ERROR_ID)
select OBJECT_ID, 0
from <KB_name>.dbo.CTV_GUID_OBJECTS
where OBJECT_NAME = 'Disconnect'
go

Info

The 0 parameter will enter 0 in the ERROR_ID column of the CI_NO_OBJECTS table.
Note that you need to specify the Analysis Service database and user as above “<KB_name>.dbo” otherwise the query will fail when the job is run.

Then:

KB Update SQL Tool - Removing an existing link using CI_NO_LINKS

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

Based on object’s ID

In this example, we are going to remove a link between two SQL objects (a T-SQL procedure called “CreateNewOrders” and a T-SQL table called “stores”) from the Analysis schema. The image below show the link in CAST Enlighten:

The first step is to check that the link exists in the Analysis schema using the CAST System Views. Use the following query in an SQL IDE against your Analysis schema:

KB Update SQL Tool - Removing an object property using CI_NO_PROPERTIES

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

Object properties can be divided into two main groups:

alphanumeric properties (for example object comments or business functions).
numeric properties (for example the number of inner comment lines, number of code lines etc.).

These can all be removed using the CAST entry table CI_NO_PROPERTIES. Properties are listed in the CAST System View CTV_OBJECT_PROPERTIES.

Based on object’s ID

In this example, we are going to remove a property from an SQL object (a Procedure called “GetTitleAuthors”) in the Analysis schema. The property we are going to remove is the Source Code Comments, which is described in the Analysis Service as “sourceCodeComment”.
You can check the value for this property by querying a CAST System View:

KB Update SQL Tool - Adding a new object linked to a parent object that already exists using CI_OBJECTS and CI_PARENTS

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

When adding a new object to the Analysis schema you MUST also define a link with a parent object. If you do not do so, an error (“The parent of the object is missing”) will be generated. See for more information on error handling.

Based on object’s ID

In this example, we are going to add a new object (a T-SQL View called “TEST”) and link it as a child to the existing database “CASTPUBS” that is already synchronized with the Analysis schema. Remember that T-SQL objects are not automatically given OBJECT_GUIDs, but this method will allow you to create your own OBJECT_GUID for the new object and will automatically create the OBJECT_GUID for the existing object (where it does not exist).

KB Update SQL Tool - Modifying an object property on an existing object using CI_INT_PROPERTIES

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

As outlined above, properties can be either alphanumeric or numeric. To modify the property of an object that already exists in the Analysis Service, two CAST entry tables are used, depending on the type of property:

Alphanumeric > CI_STR_PROPERTIES
Numeric > CI_INT_PROPERTIES

The examples in this section modify numeric properties, however it is fairly simple to modify the queries if you want to work with alphanumeric properties.

Based on object’s ID

In this example, we are going to modify various numeric properties on a T-SQL object (a T-SQL Procedure called “DeleteAllOrders”) that is synchronized with the Analysis schema.

KB Update SQL Tool - Creating new links between existing unlinked objects using CI_LINKS

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

Based on object’s ID

Objects belong to the same project and to different projects (identical for each)

This example will explain how to create a “Call” link between unlinked C++ macros (“AUTHORLENGTH” (caller) and “AUTHORSIZE” (called)) that already exist in the Analysis schema. Both objects are part of the same project (although the process for linking objects that belong to different projects is identical):

You can also check that the two objects are not already linked by executing the following query against the Analysis schema:

KB Update SQL Tool - Modifying links between existing linked objects using CI_LINKS

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

Neither objects have an OBJECT_GUID

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 example below is obsolete and should not be used.

KB Update SQL Tool - Modifying link properties

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

Introduction

Info

Available only for schemas created with AIP Core ≥ 8.3.45.

Properties on links can be either alphanumeric or numeric. To modify the property of a link that already exists in the Analysis schema, two CAST entry tables are used, depending on the type of property:

Alphanumeric > CI_STR_LINK_PROPERTIES
Numeric > CI_INT_LINK_PROPERTIES

The examples in this section modify numeric properties, however it is fairly simple to modify the queries if you want to work with alphanumeric properties. To view a list of properties that can be modified, use the CAST System View “CTV_PROPERTIES”: