Deprecated: Array and string offset access syntax with curly braces is deprecated in /homepages/12/d802028692/htdocs/forum/Sources/Subs.php on line 3863
How do I install the database on a Local Area Network (LAN)?

Author Topic: How do I install the database on a Local Area Network (LAN)?  (Read 5711 times)

Rick Leffler

  • Administrator
  • Sr. Member
  • *****
  • Posts: 263
    • Approved Workman
How do I install the database on a Local Area Network (LAN)?
« on: August 08, 2008, 10:39:57 PM »
This post only applies to the Legacy database! We now have a web-based database that is a great solution for those needing access for multiple people and/or from multiple locations.  Visit our website for more information: http://www.approvedworkman.com/awdb/cloud-database.

Note: Some wireless network connections may be too slow for adequate database performance, therefore a WIRED network connection is recommended.

Here are recommendations for installing and running the Approved Workman Database on a Local Area Network in a multi-user scenario:

1. Only have a single installation of the Approved Workman database on the server (or a PC acting as the "server"). The "Approved Workman" folder (which includes the ApprovedWorkman.exe file and the DATA subfolder) should be moved from the PC currently running THE main copy of AWdb to the shared location on the server. There is nothing to "install".
2. Share the "Approved Workman" folder and all subfolders (specifically the DATA subfolder) and set security permissions to "Full Modify" for all users/workstations that will have access to the database.
3. Do NOT install or have any other AW software on any of the workstations. Create a shortcut on the workstation that points to the ApprovedWorkman.exe  located in the ..\Approved Workman folder of the server.
4. From each workstation, launch the exe via the shortcut. If there is a message the first time about not locating the data, this is normal. Click ok and then use the folder browse dialog to navigate to and select the DATA folder on the server. Note: there MUST be a folder named "Approved Workman", with its "Data" subfolder. (Thus " ..\Approved Workman\Data" ).  UNC paths are acceptable. A drive letter does not need to be mapped.
5. From each workstation, go to Admin > Database Utilities > Database Configuration and triple the default values on that dialog.
6. Do not share usernames and passwords. Ensure EACH person has a unique name and password to log in.
7. To significantly improve performance when saving Member records, turn off the automatic refresh of the Clubber List of each workstation. Click on the Grid Options (looks like a gear) and uncheck "Automatically refresh...".  Users will need to manually click the refresh button if needed.
8. Make sure any anti-virus software is NOT scanning the Approved Workman folder or its Data subfolder.
9. Performance may be increased by turning off the opportunistic locking by editing the Registry of the server PC. If this becomes necessary, see the section below named "Opportunistic Locking".

Rick Leffler
Leffler Systems

- - - - - - - -
 
Performance Tuning on a networked multi-user installation of the Approved Workman database:
Please forward this information to your network administrator so he/she may decide if it is applicable:
 
When running the database over a network with more than one user logged in concurrently, the following information may improve performance. Try running the database first without making any of the following changes.
 
On the PC acting as the Server: (assuming Microsoft Windows XP or Vista as the O/S):
 
A: Enable Write Caching by doing the following:

1. Access My Computer;
2. Access Local Disk (c:) properties (right-click and select Properties);
3. Select Hardware;
4. Select the hard disk and click properties;
5. Select Disk Properties (might be also named Policies);
6. Enable Write Caching and Enable advanced performance.
7. Click OK.
8. Shutdown and restart the Server PC.

B: Use the Database Configuration Utility on each workstation by doing the following:

1. Log into AWdb and open the Database Configuration utility found under Admin > Database Tools > Database Configuration. 
2. Adjust the following two settings by clicking the up arrow of the spin edit component:
    Total amount of memory to use for record buffers per physical table:         98304
    Total amount of memory to use for index page buffers per physical table:  98304
    Click OK, then exit and restart the Approved Workman database.
 
Opportunistic Locking:

C: Make the following Registry Changes
    (Add the key if it doesn't exist)
<<WARNING : Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. So, don't do this if you are not comfortable editing the Registry. >>
The following Registry settings should be configured on ALL PCs:
 
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MRXSmb\Parameters\
The OplocksDisabled registry value configures Windows clients to either request or not request opportunistic locks on a remote file. We want to prevent a workstation from requesting the lock so the value should be set to 1.
OplocksDisabled REG_DWORD 0 or 1   Default: 0 (not disabled)    Set this value to 1 to disable it.
----------------------------
 
On the 'Server' PC add the following registry key:
 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
The EnableOplocks value configures Windows-based servers (including Workstations sharing files) to allow or deny opportunistic locks on local files.
 
EnableOplocks REG_DWORD 0 or 1  Default: 1 (Enabled by Default)   Set this value to 0 to disable it.
You can deny the granting of opportunistic locks on the server PC by setting the following registry entry to 0:
Reboot each PC that had a Registry change, make sure to reboot your Server PC and have it running first.
 
----------------------------


« Last Edit: March 24, 2022, 11:05:43 AM by Annette »
Rick at Leffler Systems
Murfreesboro, Tennessee