NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

clewis's avatar
clewis
Aspirant
Mar 19, 2014

Access database on the ReadyNAS 4220

A part of our organization runs a small Microsoft Access database. When I say small, I mean less than 10mb. The user group which uses it numbers about 5. I've got it set up as a split database, with one file containing the front end items (forms, switchboards, etc.) and another file containing the actual database tables. So we have "filename.mdb" and "filename-be.mdb." Further, when my users access the database they run a VBS file which takes "filename.mdb" and makes a copy of it specific to the user, such that each user ends up with "filenameusername.mdb" stored on there. I did these things thanks to the advice of people on this forum to improve performance.

For 6 years we've had this database housed on a ReadyNAS 1100. When I put the database files there, at that time, I saw the warning that I should disable opportunistic locking (aka oplocks) on the share where the database is located in order to prevent data corruption when multiple people were logged into the database simultaneously.

We have now obtained the much larger and more robust ReadyNAS 4220, and I'm not seeing a place where one can disable oplocks for an individual share. I found the SMB Plus app, but that appears to only make global changes...and I don't want to disabled oplocks on all shares.

The question is,
1. Is it really necessary to disable oplocks on a folder or share containing an Access database?
2. If yes, is there a way to do this on just a single share or folder?

At the end of the day - do I have to find a different place to put this Access database instead of placing it on this new ReadyNAS?

3 Replies

Replies have been turned off for this discussion
  • StephenB's avatar
    StephenB
    Guru - Experienced User
    Note these posts:
    viewtopic.php?t=73265#p407540 and viewtopic.php?t=73265#p407924
    Skywalker wrote:
    RAIDiator 4 only supported legacy CIFS (SMB1). We now support modern SMB2 and basic SMB3, where oplocks are not allowed to be disabled.
    Skywalker wrote:
    ...It still supports SMB1, so of course the configuration parameters will still be there. But modern clients will negotiate SMB2/3.
    From http://support.microsoft.com/kb/296264 (and various other places):
    You cannot turn off opportunistic locking for SMB2.

    We do plan to release a sort of "SMB extended controls" app, with which you can tweak more advanced settings, similar to editing the Windows registry. So when that is available (should be soon), you should be able to switch off SMB2/3 support and disable oplocks for SMB1.
    The "SMB extended controls" app is SMB Plus

    As far as I can see, the issue with oplocks when sharing MDB files on network drives continues.

    One option is to use SMB-1 exclusively, and turn oplocks off. But since your users are all copying the database it seems to me that you shouldn't see data corruption even if oplocks are on.
  • To be clear - the users are all copying the front-end of the database; they're all working into the same back-end file where the actual data tables are located.
  • StephenB's avatar
    StephenB
    Guru - Experienced User
    clewis wrote:
    To be clear - the users are all copying the front-end of the database; they're all working into the same back-end file where the actual data tables are located.
    I missed that, thx for clarifying.

NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology! 

Join Us!

ProSupport for Business

Comprehensive support plans for maximum network uptime and business peace of mind.

 

Learn More