Results 1 to 2 of 2
  1. #1
    New Lounger
    Join Date
    Aug 2003
    Thanked 0 Times in 0 Posts

    Server Speed Question

    What factors are important to increase the speed of a network server when access by client computers? Is processor speed more important than hard drive rpm or seek time? Does server RAM play a role? My network server contains a rather large Microsoft Access Database and all files utilized in Visual Basic 6 applications. My current configuration slows considerably when a VB6 applications utilizes the Access Database. Any help would be greatly appreciated! Thanks!

    Robert E. Nichols
    Attorney at Law

  2. #2
    Super Moderator jscher2000's Avatar
    Join Date
    Feb 2001
    Silicon Valley, USA
    Thanked 94 Times in 90 Posts

    Re: Server Speed Question

    How does the VB application access the database?

    Model A, the "fat client": a database engine located on the user's PC performs database joins, queries, etc., against a remote file.

    Model B, the "database server": the user's PC submits queries to a database engine located on the server.

    In Model A, you are loading the network with a huge volume of data because all operations are conducted on your user's machine. When people say you shouldn't have more than, say, 5 users sharing an Access database, they are commenting on the inefficiencies of this design.

    In Model B, which typically is implemented with SQL Server or MSDE, or through a web server using an MDB file, only queries and result sets travel over the network, and all processing is carried out at full system bus/memory/hard disc speed on the server.

    If you have Model A, and you cannot change to Model B in the short run, you can improve performance by making sure your network is as fast as possible (e.g., 100Mb switched), making sure the server hard disc is as fast as possible, and minimizing the other tasks performed by the server. Obviously lots of RAM is helpful, but unless you know you have maxed out the capacity, just adding more might not be the best investment.

    In the long run, however, you would need to rearchitect your application. This book seemed helpful (I bought it for someone else, but skimmed it first): Microsoft Access Developer's Guide to SQL Server

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts