 | |
#1
 
| |||
| |||
|
Acceptable file size -
02-22-2007
, 08:14 AM
#2
| |||
| |||
|
|
Hello everyone- I've designed a FileMaker (8.5, Windows) database for storing orders our company receives. Along with the order record itself, several other records (line items, installations, purchase orders, stored faxed documents) are created for each order. Before rolling this out onto our network I decided to "stress test" it. I ran a script to create 20,000 orders, along with a proportional number of associated records (eg 60,000 line items, etc.) What I found is that the file size increases by about 15 KB per order, so that with 20,000 orders the file is around 300 MB. My question: is this OK? Is this an acceptable and manageable size, or is it going to cause problems down the road? I just need a frame of reference. Is 300 MB for a 20,000 order database small, normal, too big? Thanks in advance for any input, Nate |
#3
| |||
| |||
|
|
Hello everyone- I've designed a FileMaker (8.5, Windows) database for storing orders our company receives. Along with the order record itself, several other records (line items, installations, purchase orders, stored faxed documents) are created for each order. Before rolling this out onto our network I decided to "stress test" it. I ran a script to create 20,000 orders, along with a proportional number of associated records (eg 60,000 line items, etc.) What I found is that the file size increases by about 15 KB per order, so that with 20,000 orders the file is around 300 MB. My question: is this OK? Is this an acceptable and manageable size, or is it going to cause problems down the road? I just need a frame of reference. Is 300 MB for a 20,000 order database small, normal, too big? Thanks in advance for any input, Nate |
There is one thing to think about: do you really need all 20,000+
records to be available?? It's often a good idea to archive old records
to another file where they aren't adding to the workload of the active
system.
Helpful Harry
Hopefully helping harassed humans happily handle handiwork hardships ;o)
#4
| |||
| |||
|
|
In article <1172153675.037801.192... (AT) t69g2000cwt (DOT) googlegroups.com>, "NScheffey" <NSchef... (AT) gmail (DOT) com> wrote: Hello everyone- I've designed a FileMaker (8.5, Windows) database for storing orders our company receives. Along with the order record itself, several other records (line items, installations, purchase orders, stored faxed documents) are created for each order. Before rolling this out onto our network I decided to "stress test" it. I ran a script to create 20,000 orders, along with a proportional number of associated records (eg 60,000 line items, etc.) What I found is that the file size increases by about 15 KB per order, so that with 20,000 orders the file is around 300 MB. My question: is this OK? Is this an acceptable and manageable size, or is it going to cause problems down the road? I just need a frame of reference. Is 300 MB for a 20,000 order database small, normal, too big? Thanks in advance for any input, Nate Ursus has already given a pretty comprehensive roundup of size limits. There is one thing to think about: do you really need all 20,000+ records to be available?? It's often a good idea to archive old records to another file where they aren't adding to the workload of the active system. Helpful Harry Hopefully helping harassed humans happily handle handiwork hardships ;o) |
#5
| |||
| |||
|
|
Thank you Ursus and Harry for your replies. So it sounds like this is an acceptable increase in file size per order, and won't render the system unusable or horribly slow over our LAN. That's what I wanted to hear. I'm also intrigued by the idea of archiving after a set number of orders, or perhaps a certain amount of time, since it is relatively rare that we will need to consult a closed order from 6 months ago (although it does happen). Would this entail creating a set of Export Records-type scripts, or is it as simple as copying the file, saving the old version, and deleting orders older than X from the new file? Maybe I should search to see if that has been covered elsewhere. Thanks again guys, Nate |
- export data to a text file (or files), but this isn't much
good for systems that have non-text data like graphics or sounds
- Save As a compressed copy to a separate file(s) then delete
old records in the original files
- copy records to a separate "archive" versions of the file(s)
- produce printout copies and then simply delete the old records
- just delete old records that are no longer needed
Usually the best time to do this is at the end of the company's
financial year so that you can start the new financial year with as
little carried over "old rubbish" as possible.
Another way, or even in addition to archiving them, is to copy the
"closed" records to a separate file.
Helpful Harry
Hopefully helping harassed humans happily handle handiwork hardships ;o)
 |
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.