Re: Converting large amount of data

My opinion would be that it would be much more efficient to write the data
and then add your logicals and you want to make sure that you create
indexes first and the logicals so that the indexes are created as SQL
indexes (Larger Page Size).

So you have a logical by company, customer number. First you create an
index by company, customer number and then the logical. The logical will
use the index and then you can delete the index.


On Fri, Jan 22, 2021 at 8:27 AM <smith5646midrange@xxxxxxxxx> wrote:

We have some files that are pretty big that we are going to be converting
to
a new format and I'm looking for some info on converting the data.



I am not looking for answers about splitting in threads or anything like
that. We are converting over 700 files so threads will not help me.
Threads will just delay other files from being converted.



That said, I have one specific question that I am looking for an answer on.



Is it more efficient to

1. Create the new physical files and their logical files, and then
convert the data

or

2. Create the new physical files, convert the data, and then add the
logical files



I know the machine has 3 CPUs with the ability to pull 3 more from the
pool.

I forget the memory but it is a pretty decent amount

There are 12 I/O channels.



If there is something else you need to know to give me an answer, please
ask.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com