 | |
new user question: database limitations for size/records
comp.databases.filemaker comp.databases.filemaker
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
new user question: database limitations for size/records -
01-30-2007
, 03:40 PM
#2
| |||
| |||
|
|
Yes, FM8.5 can handle that easily. The only thing to think of is the design of the solution that has to take into account the large number of records : one should avoid sorts on all records, for example, and make first either a 'find' or a relationship to restrict the number of record to be treated. Just yo give you an example I have a pretty complex solution in FM6 that has been working 24/7 for years with FMS(Server) 55 and 15 workstations that handles 25 files, some of which having 500 000 records (typically with 200-400 fields) with no noticeable delay in their operation. That business is renting VHS tapes and DVDs. So in short : take this into account when designing the solution, that's all. One advice, though, place the actual images or photos into separate shared folders - one file per image - and just put the 'reference' (ie the path to the actual file) into the 'Container' fields in FM, possibly in a dedicated table (for easier maintenance). Remi-Noel "Ed Marmon" <unlisted@.com.com> a écrit dans le message de news: Xns98C8A98E3E3F5edmarmailcom (AT) 69 (DOT) 28.186.158... Im looking at 8.5, and coming from CRM's such as Act! ( 2006) and Goldmine dbase ( 6.7), as well as the new MS BCM. Act! is using sql express 2005, as is MS BCM, and that has a file size limitation of 4gigs. Goldmine still uses old Borland, and that has the same 4 gig limitation. The above let you put about 50,000 contacts with reasonable notes and history ( Goldmine ) and up to 200,000 -ish for ACt!, without it starting to get slow. What are some numbers from users out there for standalone database size for *.fm7, and can I fit a good 250,000- 350,000 records on a 1-2gig ram athlon64 3000 7200RPM HD? I know, I know, it all depends on the number of fields, etc., but ballpark-wise, are we reasonably sure that FM 8.5 can handle that fine in the real world? I will use it to do periodic email blasts ( small subsets ), keep notes and histories and invoices. Business is photography and photographic supplies and products. Thanks. |
#3
| |||
| |||
|
|
Thank you. Needless to say, you wouldnt advocate something like Microsoft Business Contact Manager, with the SQL 2005 Express engine, over FM8, eh? It's nice that it's integrated with outlook email and calendar, which FM lacks, but the ability to manipulate and design the database in MSBCM... UGH, meant more for monkeys than humans... "Remi-Noel Menegaux" <rnmenegaux_AT_free.fr> wrote in news:45c02a9a$0$22587$426a74cc (AT) news (DOT) free.fr: Yes, FM8.5 can handle that easily. The only thing to think of is the design of the solution that has to take into account the large number of records : one should avoid sorts on all records, for example, and make first either a 'find' or a relationship to restrict the number of record to be treated. Just yo give you an example I have a pretty complex solution in FM6 that has been working 24/7 for years with FMS(Server) 55 and 15 workstations that handles 25 files, some of which having 500 000 records (typically with 200-400 fields) with no noticeable delay in their operation. That business is renting VHS tapes and DVDs. So in short : take this into account when designing the solution, that's all. One advice, though, place the actual images or photos into separate shared folders - one file per image - and just put the 'reference' (ie the path to the actual file) into the 'Container' fields in FM, possibly in a dedicated table (for easier maintenance). Remi-Noel "Ed Marmon" <unlisted@.com.com> a écrit dans le message de news: Xns98C8A98E3E3F5edmarmailcom (AT) 69 (DOT) 28.186.158... Im looking at 8.5, and coming from CRM's such as Act! ( 2006) and Goldmine dbase ( 6.7), as well as the new MS BCM. Act! is using sql express 2005, as is MS BCM, and that has a file size limitation of 4gigs. Goldmine still uses old Borland, and that has the same 4 gig limitation. The above let you put about 50,000 contacts with reasonable notes and history ( Goldmine ) and up to 200,000 -ish for ACt!, without it starting to get slow. What are some numbers from users out there for standalone database size for *.fm7, and can I fit a good 250,000- 350,000 records on a 1-2gig ram athlon64 3000 7200RPM HD? I know, I know, it all depends on the number of fields, etc., but ballpark-wise, are we reasonably sure that FM 8.5 can handle that fine in the real world? I will use it to do periodic email blasts ( small subsets ), keep notes and histories and invoices. Business is photography and photographic supplies and products. Thanks. |
#4
| |||
| |||
|
|
Sorry, I can't answer nor comment on what you said, I know only FileMaker and what it can do. And it is able to do a lot of this including - sometimes with the help of plugins - calendar functions and emailing. And I know also that it is powerful, reliable and pretty easy to handle to make operational solutions. Remi-Noel "Ed Marmon" <unlisted@.com.com> a écrit dans le message de news: Xns98C96143F8F79edmarmailcom (AT) 69 (DOT) 28.186.158... Thank you. Needless to say, you wouldnt advocate something like Microsoft Business Contact Manager, with the SQL 2005 Express engine, over FM8, eh? It's nice that it's integrated with outlook email and calendar, which FM lacks, but the ability to manipulate and design the database in MSBCM... UGH, meant more for monkeys than humans... "Remi-Noel Menegaux" <rnmenegaux_AT_free.fr> wrote in news:45c02a9a$0$22587$426a74cc (AT) news (DOT) free.fr: Yes, FM8.5 can handle that easily. The only thing to think of is the design of the solution that has to take into account the large number of records : one should avoid sorts on all records, for example, and make first either a 'find' or a relationship to restrict the number of record to be treated. Just yo give you an example I have a pretty complex solution in FM6 that has been working 24/7 for years with FMS(Server) 55 and 15 workstations that handles 25 files, some of which having 500 000 records (typically with 200-400 fields) with no noticeable delay in their operation. That business is renting VHS tapes and DVDs. So in short : take this into account when designing the solution, that's all. One advice, though, place the actual images or photos into separate shared folders - one file per image - and just put the 'reference' (ie the path to the actual file) into the 'Container' fields in FM, possibly in a dedicated table (for easier maintenance). Remi-Noel "Ed Marmon" <unlisted@.com.com> a écrit dans le message de news: Xns98C8A98E3E3F5edmarmailcom (AT) 69 (DOT) 28.186.158... Im looking at 8.5, and coming from CRM's such as Act! ( 2006) and Goldmine dbase ( 6.7), as well as the new MS BCM. Act! is using sql express 2005, as is MS BCM, and that has a file size limitation of 4gigs. Goldmine still uses old Borland, and that has the same 4 gig limitation. The above let you put about 50,000 contacts with reasonable notes and history ( Goldmine ) and up to 200,000 -ish for ACt!, without it starting to get slow. What are some numbers from users out there for standalone database size for *.fm7, and can I fit a good 250,000- 350,000 records on a 1-2gig ram athlon64 3000 7200RPM HD? I know, I know, it all depends on the number of fields, etc., but ballpark-wise, are we reasonably sure that FM 8.5 can handle that fine in the real world? I will use it to do periodic email blasts ( small subsets ), keep notes and histories and invoices. Business is photography and photographic supplies and products. Thanks. |
#5
| |||
| |||
|
|
Im looking at 8.5, and coming from CRM's such as Act! ( 2006) and Goldmine dbase ( 6.7), as well as the new MS BCM. Act! is using sql express 2005, as is MS BCM, and that has a file size limitation of 4gigs. Goldmine still uses old Borland, and that has the same 4 gig limitation. The above let you put about 50,000 contacts with reasonable notes and history ( Goldmine ) and up to 200,000 -ish for ACt!, without it starting to get slow. What are some numbers from users out there for standalone database size for *.fm7, and can I fit a good 250,000- 350,000 records on a 1-2gig ram athlon64 3000 7200RPM HD? I know, I know, it all depends on the number of fields, etc., but ballpark-wise, are we reasonably sure that FM 8.5 can handle that fine in the real world? I will use it to do periodic email blasts ( small subsets ), keep notes and histories and invoices. Business is photography and photographic supplies and products. Thanks. |
|
« 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.