i have change table name but constraint name is old, need to change constraint or any impact if table name is different but constraint name is old table name
Loading
i have change table name but constraint name is old, need to change constraint or any impact if table name is different but constraint name is old table name
Know the answer? Post it — somebody with the same question will find it here.
Sign in to answer this question
It is the same account you read, post and publish with — and you will come straight back to this page.
Aradhana TripathiPosted Jan 24, 2023, 4:05 PM
There will be no impact on table data, however the name of constraint may contain text of old table name and it may be confusing in future.
Aravind GovindarajPosted Jan 6, 2023, 1:22 PM
Basically, it's good to follow the custom naming convention while creating constraints like "UQ__" instead of creating automatically.
We faced the same sort of scenario in my previous project. We created a script where it will delete all the auto-created constraint name(s) and with the help of the script you can create exactly the same as previously with the changed table name.
The steps we followed while doing this activity
Hope this helps you ...
Sachin SinghPosted Jan 6, 2023, 6:49 AM
Have you faced any issue so far?
Table name change will have also updated the apporpriate Metadata in the system catalogs and so the constraint will still be referencing the correct table, so you should not get any trouble.