Which indexes/constraints are temporarily dropped/disabled during HVR refresh?

Viewing 1 post (of 1 total)
  • Author
    Posts
  • #8857
    Frank Knot
    Participant

    Which indexes/constraints are temporarily dropped/disabled during HVR refresh?

    This depends per database:

    Ingres & Vector

    * Referential constraints TO a table are dropped/created

    * Referential constraints FROM a table are dropped/created

    * Storage structure (bulk refresh)

    * Volatile secondary indexes (bulk refresh)

    * Persistent secondary indexes (bulk refresh)

    * Primary key constraints (bulk refresh)

    * Journaling (bulk refresh)

    Oracle

    * Triggers disabled/reenabled

    * Referential constraints TO a table are dropped/created

    * Referential constraints FROM a table are dropped/created

    * Domain indexes on LOB columns (bulk refresh)

    * Check constraints (bulk refresh Oracle 9)

    SQL Server

    * Triggers are enabled/disabled

    * Referential constraints TO a table are enabled/disabled (row-wise refresh)

    * Referential constraints TO a table are dropped/created (bulk refresh)

    ———————–

    All SQL statements that are needed to re-enable / re-create the constraints/triggers/storage structure is stored in the refresh recovery table:

    hvr_strr_ in the target database

    For lots of MPP targets constraints are declaration only so there should not be any issues loading into tables due to referential integrity constraints.

    • This topic was modified 3 years, 1 month ago by HVR Software.
    • This topic was modified 3 years, 1 month ago by HVR Software.
Viewing 1 post (of 1 total)
  • You must be logged in to reply to this topic.

© 2020 HVR

Test drive Contact us