That should work.
And then you can write your own update program to back-populate the
index w/o having to do a build at all.
But if your & my connivings are true, then why doesn't RocketSQ give
that to us as a concurrent build option? A few years ago they (as IBM)
declared that 7x24 uptime was a big goal for U2.
Warm regards,
Chuck
On 4/27/2011 2:24 PM, Perry Taylor wrote:
I have a need in UniVerse to add a new index on a large file which has
existing indexes. I don't have a time window in the coming days in
which to build the index but need to use the index for new records which
will be added to the file after the index has been created. Is there a
way to force UniVerse to think that the index has been built so that it
can be used for newer records allowing me to defer the build to a later
date?
Thanks.
Perry Taylor
Zirmed, Inc.
CONFIDENTIALITY NOTICE: This e-mail message, including any
attachments, is for the sole use of the intended recipient(s)
and may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is
prohibited. ZirMed, Inc. has strict policies regarding the
content of e-mail communications, specifically Protected Health
Information, any communications containing such material will
be returned to the originating party with such advisement
noted. If you are not the intended recipient, please contact
the sender by reply e-mail and destroy all copies of the
original message.
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
