G
goo
Guest
It’s around 70 tables in each database and it is 2 databases. Around 500 000 to 15 million records in each of 10 tables. The load has been running for two days on the biggest tables... as long as I can run production while doing the load, and that the Pro2 process both load and new, I am ok ... Sendt fra min iPad 16. mai 2019 kl. 09:42 skrev Valeriy Bashkatov : Update from Progress Community Valeriy Bashkatov I think yes. Basically this scenario OK. For Pro2, it depends from the amount of data. How big are your tables, how many tables, how many records are there? Which version of Pro2SQL are you using? In Pro2 v5.x there is an аlternative Bulk-Load Option for primary synchronization using a Microsoft SQL Server Linked Server. This option is applicable only for SQL Server database. You can generate SQL script files containing INSERT INTO statements to bulk load data from the source OpenEdge database. This is a faster alternative to running bulk procedures. But as far as I understand, it will not allow to start Pro2 replication processes at the same time. I haven't personally tried this feature yet, but it looks like it will speed up the initial synchronization process as much as possible. As I said before, it all depends on the amount of data and your availability requirements. P.S. FYI. I used another alternative solution but for Oracle, Pentaho Data Integration. It worked many times faster than standard Bulk-Copy in Pro2, and it took from three to ten seconds to process one hundred thousand records. But unfortunately, Pentaho couldn't handle the big data. For example, it fail with an Overflow error when it processed more than two billion records for a single table. View online You received this notification because you subscribed to the forum. To unsubscribe from only this thread, go here . Flag this post as spam/abuse.
Continue reading...
Continue reading...