Skip to content
← SQL Compare

How can we improve SQL Compare?

SQL Compare

Categories

JUMP TO ANOTHER FORUM

(thinking…)

Avoid creation of Recovery tables

Please give an option to ignore Recore tables creation. I am trying to use SQLCompare in DevOps model to avoid long release timings. But if there is any data type change to a huge table then current concept of creation of recovery tables is disabling all the FK's, removing indexes and eventually creating a new table. This is very long process and not benefitting the projects. There should be an option to avoid the creation of Recovery tables. Please think in that perspective.

16 votes
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Sarmadh shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Sarmadh commented  ·   ·  Report

    alter table add column, alter table alter column syntaxes should get executed as it is when it is moved from Source database to Destination database. instead if it create an RG table then it is increasing the overhead. Anyways REDGATE is generating explicit transaction then why do we need RG tables. It can be optional. You can provide a switch to ignore as we are ignoring many as per our need...like..ignore comments, ignore constraints, ignore keys...i am looking forward for ignore RECOVERY tables...