The JADE 2022 release meets tomorrow’s business demands.
It would be nice to have if the RPS data pump would bulk extract more smarter. Currently, we have the option of choosing a number of workers. But each worker only works on 1 class. It would be nice if a worker is finished with its list and can help with extracting of another worker, to speed up the extract. We have one class that has 15 mill instances which takes the longest to extract on rebuild. It would be nice if that was split up to 4 parts (one for each worker) to speed it up.
Thaban Segaran
Jade offers RPS extract file partitioning off the “Maintaining Extract File Names” form.
With my limited testing on this I’ve seen no improvement in the extract times using this option. I can only assume it’s because all partition workers are running out of the same node. What was the intention with this option?
https://secure.jadeworld.com/JADETech/JADE2018/OnlineDocumentation/Default.htm#resources/sdsadmin/ch2rpssupport/maintaining_extract_file_names.htm
SQL offers “File Groups”, to help with the loading of large extract files could Jade offer SQL "File Groups" within the RPS mapping. Giving the ability to invoke loads in parallel via the bulk load and alter scripts.
https://docs.microsoft.com/en-us/sql/relational-databases/databases/database-files-and-filegroups?view=sql-server-ver15