jwcolby
jwcolby at colbyconsulting.com
Wed Jan 5 12:45:01 CST 2011
This is not contact info as in Name / address / phone, it is a place to enter information about telephone (mostly) contacts with everyone that the call center people talk to. It is primarily a memo field (because they often write pages of notes) with a hand full of FKs and a few date fields. These are primarily new records (inserts) but there are edits of existing records. There are about 800 THOUSAND of these records and hundreds a day added. John W. Colby www.ColbyConsulting.com On 1/5/2011 1:21 PM, David McAfee wrote: > You can choose either path. I tend to use SQL Server security myself. > > A better question is maybe looking at the design of the table for the > contact info. > > I tend to design all data changes as insertions. Vary rarely to I allow a > table to be edited. > > I display the contact information on just about every screen, but only give > to choice to edit (if they have rights) when it is indeed needed. > > I never have locking issues in Access or SQL. > > D > > On Wed, Jan 5, 2011 at 10:00 AM, jwcolby<jwcolby at colbyconsulting.com>wrote: > >> I am having performance issues in a largish Access application, a >> Disability Insurance Claim call center app. >> >> I have one particular table which is not huge in terms of field count but >> it does have a lot of records and most of the fields are indexed, and it has >> about 800K records in it. This table holds "contact" info, as in phone >> calls that the users have. They document every "contact" with every one, >> claimants, doctors, lawyers, etc. into a memo field and also date of call, >> ClaimID FK, employee id FK, contact type id FK etc. Kind of a mini center >> of the universe for this application. >> >> The result is that people are storing new records in this table constantly >> throughout the day and we are getting a lot of "record locked..." issues >> caused by (AFAICT) the time it takes Jet to store the records and update all >> of the indexes, and probably the memo storage area of the mdb. >> >> Just to give a picture, this one table has been moved out to it's own mdb >> and that mdb is about 700 megabytes after a compact. Most of the rest of >> the database (150 tables) is in another mdb and after compact that database >> is 800 megabytes, so this one table is close to as big as the rest of the >> db. >> >> I do not have experience in a transactional database using SQL Server, but >> I am thinking that SQL Server express 2005 will not have an issue keeping up >> with this kind of usage - 25 users adding records to this table all day >> without causing locking issues like I am seeing now. >> >> My issue at this point is that they use a network logon and force the users >> to change their password every 30 days. Is SQL Server going to use that >> same network username / password database or does it use a list of usernames >> / passwords physically on the server itself? IOW will Windows >> authentication work or will I need to go to SQL Server username / password? >> >> -- >> John W. Colby >> www.ColbyConsulting.com >> _______________________________________________ >> dba-VB mailing list >> dba-VB at databaseadvisors.com >> http://databaseadvisors.com/mailman/listinfo/dba-vb >> http://www.databaseadvisors.com >> >> > _______________________________________________ > dba-VB mailing list > dba-VB at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-vb > http://www.databaseadvisors.com > >