Why does Omni Security recommend using a Ctree Cache table when running with SQL Server?
SQL Server is not suited to the type of access that Omni Security uses for the Cache Table. It was found that shifting the Cache table to Ctree gave a significant boost (up to 10 times) in the performance of the Cache table. It is recommended that a Ctree cache is used with Great Plains SQL versions systems. The location of the cache is configured on a system or per machine basis and can be set up via the Omni Security >> Options window, or can be edited in the DEX.INI file. It is suggested that, for best performance, the location be local to the workstation performing most of the security work and shared to all other workstations. Another method of forcing Omni Security to ask if you want to use a Ctree cache like it did when you first installed is to manually delete the contents of the WDC51101 table in the DYNAMICS database on your SQL server. Use the Transact SQL statement delete from DYNAMICS..WDC51101. Note: Please ensure that all workstations point to the same folder for the Ctr
