How paritioned tables are compared in oracler schema compari

gahuja

How paritioned tables are compared in oracler schema comparison?

1)E.g. if in Source Table 'A' have 12 paritions Jan-Dec,In target Table 'A' has 8 paritions Jan-Aug...will the compairson deployment script will create remaining paritionings in target script
This is range paritions...How does Redgate schema comparison behaves in hash and list partitions

2)If the paritioning key is different between source and target,will it capture the change in schema comparison....?

Kindly suggest

richardjm

The best way to find this out is to try it on an example. Our storage options aren't very mature and I'm currently working on them but it's taking a lot longer than I'd have hoped.

The upcoming version does have improved support for storage options.

In your cases it *should* cause a table rebuild to reconfigure the partitioning if the "Ignore storage" option is turned off (on by default).

if you have issues with it let me know and I can give you access to the latest build which should do better.