Results 1 to 4 of 4
  1. #1
    Join Date
    Apr 2004
    Posts
    88

    Access DB on Windows 2003 issue

    Hello,

    The company i work for is installing their application on a clients Windows 2003 server. The application uses an ms access database.

    The issue we are running into is that whenever the application needs to read from, or update the database, the database somehow gets locked up and the server needs to be restarted to fix the database locking. Though once again database read/write causes it to lock up.

    This hasnt been an issue with our hosting which is off of infoquest.com, and this is the first time it has cropped up.

    I know access is not the best of databases, and for now i cant do much about that. Just thought some of the guru's here may have an answer.

  2. #2
    Join Date
    Jul 2004
    Location
    Vladivostok, Russia
    Posts
    211
    check your code.... usually it means that some of your scripts gets exclusive access to the database and doesn't close the connection
    http://bandwidth-control.net
    Farpost Inc.
    IT outsourcing by certified professionals.

  3. #3
    Join Date
    Jan 2005
    Location
    Chicago
    Posts
    226
    At least years ago, Access used to lock the database it connected to over ODBC and if Access died or the connection was lost, your database froze up since the lock was never released.

    The obvious question is, did anything change when the app broke?- New settings, extra clients etc?
    Ken

    CROWHOST hosting+colocation services | 877-CROWHOST | support at crowhost.com
    Independent remote-hands serving all Chicago data centers

  4. #4
    Join Date
    May 2005
    Location
    Bohemia, NY
    Posts
    61
    Access is not suitable for production systems where concurrent usage is an issue. No matter what precautions you attempt to take, it will do this, because it is just a set of drivers for Microsoft Jet through ODBC that allow the open process to deal with the file directly. It does not manage concurrent connections as a proper socket-based RDBMS would. If you don't run into errors, you do hit performance problems pretty early, as Access loves to lock tables whenever it does anything, and occasionally the entire database as well, which you now have to wait on.

    The ideal long-term solution would be to migrate to a better RDBMS. PostgreSQL and MySQL are both free, and the latter at least is good. MySQL is nothing phenomenal, but it's worlds better than Access for anything beyond secretary work.

    In the short-term, you may want to investigate the code and make sure all connections are being closed. If the database connection is being defined in a session-specific context somewhere, like a global.asa file, don't do that. You may also wish to consider ODBC connection pooling, which may or may not help you.
    Interkey.net Technical Support

Posting Permissions

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