For our Virtual Office and Hybrid RDB clients, please contact us via the MyAccess portal and reference the title of this article.
For clients hosting their own Access RDB database, management of transaction logs within SQL is a function of your environment within which Access RDB operates, and as such not covered by pure RDB technical support. However, you may wish to forward the following information to your IT provider which should help them resolve the issue. To be checked:
Is there a daily (or other suitable frequency) maintenance plan in place for Access RDB (by default named "ProNet") database.
Does this maintenance plan include a step to truncate the transaction log at a suitable point (after a successful backup, for example).
Is the scheduled SQL job for running the maintenance plan completing successfully.
..and subsequently check:
Does the transaction log have adequate allocated server storage space, and is there enough space on the specified drive to easily fulfil that allocation.
Should your own IT resources not have the SQL expertise necessary for checking and rectifying the above, please speak to your Customer Success Manager or Account Manager who can pass your details to our Professional Services team who would be able to assist you. This will most likely be a chargeable service.