Odd partioning behaviour

Where I have a table that is partioned and this has partitioned indexes if the column used by the index for the partitioning scheme differs from that used by the table then SQL Compare incorectly thinks that column is used by the tables partition.
I will see if I can work out a small sample script for you that demonstrats this.
I will see if I can work out a small sample script for you that demonstrats this.
Comments
This doesn't ring a bell as a known problem, but it's a pretty specific scenario you're describing. If you're able to send an example over to us at [email protected] with F0072294 in the subject line, we can validate the behaviour and log a bug as necessary.
Redgate Software