very low-traffic = maybe 2-3 records added a day max. The number of records will probably never exceed 1000. Relatively high traffic = I don't know, 5- 6 simultaneous users, up to 1000 records updated a day. The number of records could conceivably get very high in this second case. I am trying to design so that only simple queries are required in both cases.
Dana On Sun, 08 Jun 2003 07:26:58 -0400, Jochem van Dieten <[EMAIL PROTECTED]> wrote: > Dana Tierney wrote: >> so... in your opinion mySQL would not be an improvement over Access say? > > Unless there are reasons why Access simply won't work (like you are > running Linux). > > >> 1. A patient registry which while be almost entirely character data and >> booleans. Some counters. Will be very low-traffic. I am using mySQL for >> this. > > You should be able to run that on Access without a problem. > > >> 2. A patient system which should be scaleable and capable of being >> modified >> for fairly high security. Again, will handle primarily booleans and >> character data, but must be able to accomodate medium to high traffic. > > How do you define high traffic? How many queries per second, and what is > the insert/update/delete/select ratio? How complicated are the queries? > Just retrieval based on the primary key, or complicated multi-table joins > with functional predicates? > > Jochem > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=5 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=5 Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.5
