|
|
| (не показано 11 промежуточных версий этого же участника) |
| Строка 1: |
Строка 1: |
| − | [http://devzone.advantagedatabase.com/dz/webhelp/Advantage10.1/master_non_exclusive_proprietary_locking.htm Non-Exclusive Proprietary Locking]
| + | В старых версиях ADS не использовала эксклюзивный режим доступа к файлам, а использовала режим "запрет записи". Это позволяло сторонним приложениям получить доступ к данным, но могло привести к повреждению индекса. Сторонние приложения могли блокировать некоторые части в файле, что приводило к ошибке чтения и записи со стороны ADS. По этой причине был изменен режим доступа к данным при блокировке по-умолчанию. |
| − | | + | Теперь используется '''эксклюзивный''' режим доступа '''по-умолчанию'''. |
| − | В старых версиях ADS не открывала файлы, используя эксклюзивный режим, а использовала режим "запрет записи". | + | Для нормальной работы фабиуса '''необходимо''' переключить этот режим доступа в '''не эксклюзивный'''. |
| − | | + | |
| − | While this would allow non-Advantage applications access to the data files, it could also lead to index corruption. Non-Advantage applications could still lock bytes in the files causing Advantage read and write operations to fail. For this reason the default proprietary open mode '''was changed'''. If, however, you require other non-Advantage enabled applications (such as backup software or reporting software) to open files in a shared, read-only mode, this server option is available to revert to older behavior.
| + | |
| − | | + | |
| − | For more details on proprietary locking, see '''Advantage Proprietary Locking'''.
| + | |
| − | | + | |
| − | To turn off the exclusive proprietary locking file open mode, perform one of the following
| + | |
| − | | + | |
| | = For Windows = | | = For Windows = |
| | Add the following DWORD using the Registry Editor (REGEDIT.EXE) into the registry, and set its value to 1. | | Add the following DWORD using the Registry Editor (REGEDIT.EXE) into the registry, and set its value to 1. |
| | | | |
| | \\HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Advantage\Configuration\NONEXCLUSIVE_PROPRIETARY_LOCKING | | \\HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Advantage\Configuration\NONEXCLUSIVE_PROPRIETARY_LOCKING |
| − |
| |
| − | = Advantage Proprietary Locking =
| |
| − | The [[Advantage Database Server]] uses an intelligent lock management system with its proprietary locking mode that eliminates lock retries and requires no network traffic. The [[Advantage Database Server]] uses an internal queuing algorithm that allows application locks to occur without making network operating system lock API calls. All locking information is maintained internally in the lock queues.
| |
| − |
| |
| − | Advantage Proprietary locking mode also allows for read-through index locking and immediate index write locking. When an index is being read, there is no danger of that reader changing the structure of that index. Thus, Advantage allows read-through index locking for index "read" locks. All users who desire to read the same index can get concurrent "read" locks on that index and read from the index all at the same time. As you can imagine, this increases multi-user index "read" performance immensely. When an index is being updated, it is possible that the structure of the index may change. Thus, when a user obtains a "write" lock on an index, no other users can obtain a "read" or "write" lock on the index. The Advantage queuing process allows users to "line up" for access to that index. As soon as the user is done updating the index and releases the "write" lock on the index, the next user in the queue will immediately obtain an index lock and can proceed with the index read or write operation. No lock retries are ever required. "Write" lock requests are simply queued, and the locks are immediately granted as soon as the prior user has released the lock. This "write" lock queuing and elimination of lock retries increases multi-user database application performance.
| |
| − |
| |
| − | Advantage Proprietary locking is only available with the [[Advantage Database Server]]. Advantage Proprietary locking is not available with the Advantage Local Server.
| |
| − |
| |
| − | When Advantage Proprietary Locking is used, files are opened in an exclusive mode. Since the files cannot be opened by non-Advantage users, the Advantage Database Server can assume the environment is Advantage-only and internally maintains specific locking information
| |
| − | Non-Advantage applications can not open the files
| |
| − | Likewise, the [[Advantage Database Server]] cannot open files that were opened by some other application.
| |
| − |
| |
| − | When Advantage Proprietary Locking is used on Advantage ADT files, index "write" locking can be performed per tag. Therefore, multiple applications can be updating different tags in the same ADI file at the same time. This per tag "write" locking is not available with Xbase index files.
| |
| | | | |
| | = Смотрите также = | | = Смотрите также = |
| − | [http://devzone.advantagedatabase.com/dz/webhelp/Advantage9.1/non_exclusive_proprietary_locking.htm Non-Exclusive Proprietary Locking] | + | [http://devzone.advantagedatabase.com/dz/webhelp/Advantage10.1/master_non_exclusive_proprietary_locking.htm Non-Exclusive Proprietary Locking] |
В старых версиях ADS не использовала эксклюзивный режим доступа к файлам, а использовала режим "запрет записи". Это позволяло сторонним приложениям получить доступ к данным, но могло привести к повреждению индекса. Сторонние приложения могли блокировать некоторые части в файле, что приводило к ошибке чтения и записи со стороны ADS. По этой причине был изменен режим доступа к данным при блокировке по-умолчанию.
Add the following DWORD using the Registry Editor (REGEDIT.EXE) into the registry, and set its value to 1.
\\HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Advantage\Configuration\NONEXCLUSIVE_PROPRIETARY_LOCKING
