Upgrading from SQL Anywhere 11 to SQL Anywhere 17

[Former Member]

we have a client base that has been in limbo for a long while. Is there any documentation that relates to this process, and the order in which table data is replicated. Would it be easier to upgrade to 12 first and then upgrade to 17 and if so is there anywhere I can get a copy of 12 ?

Terry

[VolkerBarth · Accepted solution]

If a child table falls into either of these characteristics it will fail on the foreign key relationships as defined.

That comes as a surprise:

In my understanding and experience, DBUNLOAD does always

1. create tables without FK definitions,
2. loads the data,
3. and then finally uses ALTER TABLE to add the FK definitions,

so – unless there already are RI violations present in the actual data – there should be no problem with table order... That order of operations has been unchanged for many versions, methinks.

Do you use a particular DBUNLOAD command?

----

Aside: Or do you use CHECK constraints that rely on data in different tables? Those CHECK constraints are declared within the CREATE TABLE step, so in that case the table order may matter because the check constraints will already be checked during the data load phase...

----

EDIT: I turned my comment into an answer just because it might get overlooked otherwise...