Our scenario isn't so much outgrowing its design as expanding upon its design. Basically what happened was due to accounting requirements, we had to make a change to our company's inventory process to move it from a mixture of serialized parts (for large-ticket items) and non-serialized parts (for small-ticket items) to have everything be serialized. Combined with the fact that some of the orders our customers place have line items with small-ticket items where quantities range into the multiple thousands, this causes very large amounts of data to be stored in the serial number field of the records.
We are already seeing a performance hit in certain areas with these instances. Fortunately they are not completely common occurrences, but they do occur frequently enough that we have had two or three instances of connections timing out on some of our users since we made the conversion three months ago. Adam Taylor Program Manager 713.795.2352 www.INXI.com -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Charles Stevenson Sent: Thursday, April 23, 2009 12:12 PM To: [email protected] Subject: Re: [U2] Record Size Limit in UV I've seen records at least an order of magnitude larger than that. Unix & Windows. Megabytes. I want to say much larger than that, but I can't verify that and when numbers get that big, my brain can't get around them. ( e.g., $1,000,000,000,000: www.pagetutor.com/trillion/index.html ) I don't know of absolute limits, but performance takes a dive, of course: lock contention, frequent updates, inappropriate indexes, selections w/o indexing poorly sized files (they should be type 30, if they must exist. The large records get isolated in their own overflow). In general, U2 responds well to size abuse. Performance degradation is fairly linear & responds well to throwing more hardware at it. But at some point degradation curve becomes geometric. I'm curious about whether your scenario matches the usual: i.e., an application that has outgrown its original design, with a multi-valued association in that gets updated frequently through the lfe of the record. The original design intended a few mv entires, until the business operation it represents gets closed. At some point someone decided to use the association for some additional purpose. Some records remain small, some grow, resulting in a very lumpy file. Many times it's the users trying to respond quickly to a changing business need, w/o waiting for IT to do the enhancement (they invent new status codes, etc.). Sometimes it's programmers enamored by the siren call of mv nesting. Adam Taylor wrote: > Hey all, > > Can anyone tell me what (if any) the current record size limit is in UV 10.2? > We've currently found ourselves in a situation where certain fields in a data > file will contain 100K+ characters and we would like to be proactive about any > potential problems if they exist. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ IMPORTANT/CONFIDENTIAL: This message from INX Inc. is intended only for the use of the addressees shown above. It contains information that may be privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient of this message, you are hereby notified that the copying, use or distribution of any information or materials transmitted in or with this message is strictly prohibited. If you received this message by mistake, please immediately email or call us collect at (469) 549-3800 and delete/destroy the original message. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
