Devart Forums

Hi,

I've just done a schema compare between two databases and as part of that dbForge identified a table needed to be rebuilt as it couldn't be altered without data loss.

When reapplying the indexes it makes the correct choice regarding the tablespace to use, but when applying the constraints back it tries to use a tablespace from the source database and not the target.

Any ideas on how to overcome? I've emailed support but not sure how fast they'll respond. I've selected it ignore tablespace and storage clauses.

Could you please provide us the scripts and describe it step by step?

You can send the reply straight to our support system at supportATdevartDOTcom.

We were able to reproduce this issue and will fix it in one of the next product builds. We will notify you on it.

Hi Alexa,

This is a serious issue for us. It essentially renders the schema compare useless. Given there hasn't been a build since December when can we expect it to be resolved?

It should be released in about a month's time.