|
QSA ToolWorks Public Feedback Forum forum home | register | profile | members |search | faq homepage | lost password? | chat room |
| QSA ToolWorks Public Feedback Forum > General Helix Talk > Real Helix Upper Limitations | You are not logged in. Login or Register. |
| Pages: 1 |
| Author: | Topic: Real Helix Upper Limitations | |||
| SGC Posts: 1 Registered: 2003-08-15 sgcexernet |
I was a heavy duty Helix user a long time ago. I built the operations of my entire business around Helix. We used a Helix database for inventory, invoices, all report generation, payroll yada-yada-yada. I now have a new business. The core of the business is a customer database that maintains many records for each customer. We currently have an over-engineered database that is based entirely on Microsoft technology. I am very dissatisfied with it’s inflexibility and the difficulty in making quick changes in response to customer needs. I used to LOVE the flexibility and speed of development with a Helix based system. In other words – I would LOVE to be a customer for the new OS X version of Helix. I am an AVID fan of OS X and I would love to switch all aspects of my business over to this very robust and deep OS. But first I have a few questions. The most import of which is: What kind of a record load can Helix handle? For example, if a collection had 5 million records in it, could Helix handle it? When would Helix run out of gas? Could it rapidly find a record among 5 million records. (Assume the latest and greatest in Apple Hardware) Is there a way to distrute Helix over a server farm? Can anyone give me some examples of large collections (size (number of records) use, special considerations anything) Is there a list of large Helix applications somewhere? Is there some place where the real and or theoretical upper limits of Helix are published? |
|||
dkuchta![]() Posts: 40 Registered: 2003-04-09 |
SGC: (Nice shades, by the way :-) I don't have an answer for you, but I would like to suggest you try joining the Helix list at: http://maelstrom.stjohns.edu/archives/helix-l.html That gets a MUCh broader readership than these forums do. You won't get bombarded with too many emails from the list. The average load is 3-5 per day, although sometimes you don't get any for a few days, and other times you might get as many as 10-15 if a particularly controversial topic is raised. In any case, you'll very likely find people who have some answers for you there. -Dan Kuchta
|
|||
| Sven Posts: 24 Registered: 2003-04-09 |
One upper limitation which comes to mind is that Helix has a 2 gigabyte file size limit. There is a discussion on this limit on the Helix website at http://www.helixtech.com/1Product/Helix6/h6030529.html. I think I recall from a thread on the Helix list, that it was confirmed that there is a limit to the number of records (current and deleted that is) which have existed in a relation. Was it four billion?. It is unlikely that this will become a problem unless one uses batch deleting and importing of huge number of records on a recurring basis.
|
|||
Matt![]() Posts: 107 Registered: 2003-02-16 mstrange@mac.com |
Just discovered: the total number of forms, sequences, and users in a collection can not exceed 3,640. Actually, it can, but the User Editor breaks. The fix will have to wait for Helix 6
|
|||
| keVin Posts: 30 Registered: 2003-04-09 |
quote:Some Collections are over 30 years old. What are the observable characteristics and/or remedies after reaching this threshold? |
|||
| Fred Posts: 57 Registered: 2003-04-10 |
Hi keVin, quote: What were you programming on 30 years ago ![]() I think the amount of records in a relation probably depends on the "invisible to some" record id number type. Or does it restart from zero once the limit reached?? PS Nice to see someone here now and again.. |
|||
| Sven Posts: 24 Registered: 2003-04-09 |
About three years ago, there was a discussion on this on the Helix List. Matthew Strange wrote "FYI, the total number of cumulative records a relation can hold is (I think) 4,294,967,295. By cumulative, I mean the sum of all records (current and deleted) that have ever existed in the relation. Just in case that actually worries somebody, should such an event occur, we could tell you how to reset a relation so that the previously deleted records didn't count anymore." Sven
|
|||
| keVin Posts: 30 Registered: 2003-04-09 |
quote: I received a Collection from someone with a creation date (Get Info) in 1970. Though I didn't do the math to realize there was no Helix back then, it made me wonder about Helix outer limits. Apparently in this case the user's system clock was not set properly. However, it is a pretty old Collection.quote: Comforting. I was questioning what the symptoms of this eminent demise were. As best I can tell from the post, Helix will not accept another record. Perhaps the Collection will not launch. I was wondering if there might be some observable behavioral characteristics (e.g.: posts do not fire, unpredictable display on lists, error codes?). |
|||
| ercoguru Posts: 4 Registered: 2004-09-12 |
Hi all, I'm still running Helix Express 4.5.1 in Classic mode on a 900 MHz iBook and OS 10.3.5, and keep a collection of approximately 3,000 registered owners of a certain type of vehicle. To update this information current, I must download a database of 355,355 owners and then separate out my 3,000. These are then dumped and loaded into an interim collection which modifies the information into a format suitable for my uses. I presently use a new template each time, so there is no accumulation. The master database contains 24 data fields for each owner, or a total possible of 8,528,520. Using a Verizon cell phone (Samsung a530), a download takes about a half hour. Loading the information (offline) into my template in one chunk has not been possible. I get an error just before completion (after approximately 12 hours). My solution has been to split the information into three chunks (two didn't work either) and upload each separately. I seem to recollect my source saying that this database too big for Excell. Anyway, the preceding are some on-topic numbers and experience to kick around. BTW, I could also download only added, deleted and changed (mostly addresses) owners on a weekly basis. To update a "master" collection, I suspect automation possible only to a "live" scan-and-stop (on change in any owner for manual field review/substitution). Don't know how to set that up, but would probably be an improvement over present practice. Ideas welcome off-list! Regards,
|
| Pages: 1 |
| Lost Password? Powered by UPB Version : 1.8 A script by PHP Outburst |