You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Sequence Handling During Table Refresh

in Database 1 comment

Hi Team,

How should we handle Oracle sequences when refreshing tables from production to the test environment?

  • If we use CONTENT=DATA_ONLY with TABLE_EXISTS_ACTION=TRUNCATE, will the existing sequences remain unchanged?
  • How can we identify which sequences are associated with the tables being refreshed?
  • Should we retain the existing test sequence values or synchronize them with production?
  • If the table uses a sequence to generate primary key values, how can we ensure the next generated value does not conflict with existing records after the refresh?
  • What is the recommended approach for handling sequences, identity columns, and associated triggers during the refresh?
Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!