Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Modules / DAO / VBA / October 2004

Tip: Looking for answers? Try searching our database.

Need Advise on speeding up db's - Regarding Access / SQL Server / Network / Win 2000 Server

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Jado - 13 Oct 2004 12:57 GMT
Hi

We run a small outbound call centre with around 20 agents.

usually there will be 10-15 indevidual projects on the go, each contained in
it's own Access 97 DB.

All Access DB's on held on a single Win 2000 PDC Server.

The numbers of records in a single db will be anywhere from 3,000-12,000

Under these circumstaces, everything usually works just fine, with next to
no speed issuse.
------------------------------------
Currently we are working on 2 large projects with upto 8 agents working on
each.

both projects contain over 100,000 records with one on them using a large
number of Fields.

Project1 = 95MB
Project2 = 150MB

we are also running arround 5 other normal sized projects.

All of the agents on the 2 large projects are now experiancing serious speed
problems.

The main issuse is moving through the records which can take upto 20 seconds
per record viewed.

--------------------------
Access 97 DB Info
--------------------------
All the DB's are created from a Template DB with a simple design.

All the data is stored in 2 tables with a 1 to Many relationship
Table1 = Company Info
Table2 = Contact Info

i.e 1 [Company] can have many [Contacts]

Again, Form design is simple using a single [Company Form] with an embeded
[Contact subForm]
--------------------------------------------
solex - 13 Oct 2004 16:39 GMT
What do you mean by a large number of fields?  Also it has been my
experience that using access with more then 5 concurrent users is generally
not a good idea for performance reasons (this depends upon the complexity of
the data model and the amount of records)

Perhaps you should consider using normalization also why do you mention SQL
server in the subject when you are not using SQL server?  Have you examined
the performace using the performance tools under the menu
"Tools\Analyze\Performance"?

> Hi
>
[quoted text clipped - 41 lines]
> [Contact subForm]
> --------------------------------------------
david epsom dot com dot au - 14 Oct 2004 05:22 GMT
I find no problems selecting a single record from a single table
with a database that size. I do see delays up to 1 second using
FindFirst on a recordset with several tables joined to a large table.

I do see delays up to several seconds for forms with several
combo-boxes on slow networks.

Can you give more details about what is slow?

Also, have a look (if you have not yet done so) at Tony's
Microsoft Access Performance FAQ
http://www.granite.ab.ca/access/performancefaq.htm

(david)

> Hi
>
[quoted text clipped - 41 lines]
> [Contact subForm]
> --------------------------------------------
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.