JWColby
jwcolby at colbyconsulting.com
Tue Oct 31 09:48:22 CST 2006
Oh well. I have a client with a database with well over 500 mbytes of data. I did break it down but I did it for technical reasons having to do with one table having a bunch of memo fields and lots of activity, which was causing bloating. I wanted to be able to compact and repair the pieces individually. The main database container in this specific application currently sits at about 250 mbytes, and has ~40 users in it all day. It is a mission critical database for a disability insurance call center. I designed it from scratch starting in March 2002 and it has been in operation since the first week of August, 2002 (I just checked my billing database). They add about 100 mbytes of data per year and (so far) have all the claims processed still on line. In the past months we have brought up a claims payment module that allows actually paying the claims through a payroll processing third party. We are about to bring another insurance client on board that will require similar claims payments processing. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gowey Mike W Sent: Tuesday, October 31, 2006 9:21 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Record Maximum Thanks guys for your input. I was just looking for some ways to explain to the customer that the rumor that they heard about Access databases crashing when the size of the database reached over 100mb. I already explained that this was a vicious rumor and explained to them how it works, but they were not totally convinced so I was looking for more amminition to though at them to eleviate their concerns. Thanks again -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of William Hindman Sent: Monday, October 30, 2006 5:36 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Record Maximum ...as JC pointed out, the "number" of records is rarely the driving factor ...I'd add to JC's comments that the record length plays into the issue as well ...if each record is 2k its a major factor in your considerations. ...and while record count IS a factor in archiving, its not THE major factor ...I baseline archive a record whenever it meets certain client specific milestones and only IF the client concurs on a record by record basis ...a dead record is a dead record whether there are 2K or 2M of them William Hindman ----- Original Message ----- From: "Gowey Mike W" <Mike.W.Gowey at doc.state.or.us> To: "Access Developers discussion and problem solving" <accessd at databaseadvisors.com> Sent: Monday, October 30, 2006 4:38 PM Subject: [AccessD] Record Maximum > > > Hi Everyone, > > Just a quick question. What is the maximum or the most records that > anyone has seen in a table before the database started to degrade in > permormance. > > What would you consider the maximum record count before archiving? > > > TIA for your thoughts, > > Mike Gowey MCP, MCDST, MCSA, A+, LME, NET+ Team Leader - SouthEast > Region Information Systems Unit > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com