We are close to starting our first implementation of Axapta. It's a
relatively small implementation with all users resident on the same
LAN. We'll be using an AOS with thin clients.
I want to turn all caching off from the start and only activate as
performance requirements increase/concerns around caching decrease.
In order to switch off all caching, will the advanced switch
of "internal=maxCacheLevel:0" suffice? If not, does table caching
still have to be disabled under user options and record caching using
the property on the tables in the AOT ?
Any comments or recommendations?
SPONSORED LINKS
| Computer part | Programming languages | Microsoft axapta |
| Support exchange |
YAHOO! GROUPS LINKS
- Visit your group "development-axapta" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
