Closed giubari closed 5 years ago
If you mean to do an incremental update then no, that feature is not supported at this time.
Running the dml
command will copy all of the data over from the beginning. Unless you have a really huge database that is usually done in a relatively short period of time, assuming no major network latency between the servers.
Ok thanks. We're talking about 200k rows but for now I'll stick to a midnight run. Thanks for the quick reply.
Il giorno mer 2 gen 2019 alle ore 23:05 Igal Sapir notifications@github.com ha scritto:
If you mean to do an incremental update then no, that feature is not supported at this time.
Running the dml command will copy all of the data over from the beginning. Unless you have a really huge database that is usually done in a relatively short period of time, assuming no major network latency between the servers.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/isapir/Migrate2Postgres/issues/8#issuecomment-451000027, or mute the thread https://github.com/notifications/unsubscribe-auth/AKSTIceNaMXec8pSmtGLZui-jeVZB4C1ks5u_S1EgaJpZM4ZnSQJ .
I have moved millions of rows in a matter of minutes, but if you want to minimize the downtime then you definitely want to plan for a time when usage is low and notify everyone ahead of time.
Hi, is possible to reuse the batch just to update the database\table after migration?