OnDemand User Group
Support Forums => Report Indexing => Topic started by: DDP021 on October 09, 2018, 02:44:51 AM
-
We have a report where the application has 26 (yes 26) indexes. This is a text report. When we run it through the Report Wizard it sets all the indexes to BREAK=YES. We have many reports that are generated from the mainframe and sent to CMOD. When these reports were initially converted to CMOD years ago, we've noticed, on their indexing, some fields are set to BREAK=YES while others are set to BREAK=NO...We know there has to be a rational for doing this but never really understood what that is. Looking for any explanation....;-)
-
The 'BREAK' parameter determines if a change in that field will result in the creation of a new document (a new database row, with new metadata, etc.).
You'd want to break on customer number, but not on another field, say, for zip codes, as you may have more than one customer per zip code, and don't want all customers inside that zip code to be able to see each other's documents.
-JD.
-
Correct me if I am wrong, it has been a few years..
On something with that many fields, and Break=yes to all, wouldnt that take a LONG time to index? Depending on the file?
-
Correct me if I am wrong, it has been a few years..
On something with that many fields, and Break=yes to all, wouldnt that take a LONG time to index? Depending on the file?
More breaks = more documents = more index rows = more inserts into the database = more time. :)
But it shouldn't be a huge problem. CMOD is built for this sort of thing.
-
Thanks Justin!....Your explanation does clarify things...This particular application is quite large....We questioned them prior on whether it was a need for so many indexes and they indicated they use all of them for searching in order to get to the exact information they need...As always, thanks for the info!...Take care....Dave
-
CMOD is built for this sort of thing.
I'll remember this ;)