Open topic with navigation

TIBCO BusinessEvents® Enterprise Edition 6.3.1

# What the Schema Update Utility Can Handle Automatically

You must examine the altered script before you run it. Decide what changes to make manually and what changes to make using the script, considering the kind of data in the tables. Entries that could result in data loss are commented. Remove or comment entries for changes you do manually.

Restriction: You cannot change the type of the field for ActiveSpaces and Apache Cassandra.

## Adds

The schema migration utility handles the addition of entity types and attributes. New entity types and attributes are added to the database schema.

Changes (Drop and Add)-Assess individually
The utility handles changes to attributes (entity properties) as `DROP` and `ADD` operations. However, `DROP` operations are commented in the script to avoid data loss.
If a column is empty, or you do not want to keep the data they contain, you can enable the `DROP` operation and let the utility handle the change.
If the column contains data that you want to keep, then make the change manually by using an appropriate database tool. For example, you can change the data type of a column from string to double without loss of data, as long as all the column values are numeric values.
Entity Deletions
If an entity is deleted from the TIBCO BusinessEvents Studio project, the corresponding tables are not dropped from the database schema. Existing data is not lost. Deleted entities are not mentioned in the alter script. Manually monitor and delete such tables as needed.
Attribute Deletions
The schema update utility does handle deletion of entity attributes. SQL statements for deleted attributes are generated but they are commented. Examine the altered script and enable these commands if you want to run them. Note that existing data is lost when you drop an attribute.

## Example Alter Script

Below is an example `yourname_alter.sql` script.

Property type change

    --  ##### WARNING :  Non-alterable Ontology changes found. Please see following errors. Manual schema-migration is required.
    --* For Concept Concept1 field PROPERTY_1 type changed from VARCHAR2 to LONG
    -- ALTER TABLE D_Concept1 DROP ( Property_1 );
    ALTER TABLE D_Concept1 ADD ( Property_1 numeric(19) );
    New table
    DROP TABLE D_Book_rrf;
    CREATE TABLE D_Book_rrf (pid numeric(19), propName char varying(255), id$ numeric(19) not null);
    New property
    -- ALTER TABLE D_MyConcept DROP ( FOLDER_1 );
    ALTER TABLE D_MyConcept ADD ( Folder_0 char varying(255) );

Did you find this helpful?

YesNo
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO BusinessEvents® Enterprise Edition

Copyright © 2004-2024. Cloud Software Group, Inc. All Rights Reserved.