Hi everyone,
I have an interesting query about the table cache settings (well I think it is interesting at least). Now if I have a table such as item master that is set as FULL I understand what is going to happen (and I believe Harry gave an interesting find about if the data that needs to be cached gets too big what can happen) but I was wondering what happens as I add a new record to such a table? Does Axapta decide it has to revoke all users who have cached the table and issue them a new one? Does each AOS user need this revoke and reissue or is their some central cache used for these tables? I know AOS will cache but I am not sure whether it is more a 'dumb' disk read cache or a more intelligent pooled table cache? My final and main query is if such revoking and reissuing is going to happen what impact is it going to have if say I am importing 1 million item master records? Will it be doing this revoke and reissue for every record (i.e. what is the overhead in an import situation)? I guess it also depends on when I commit the records but let's say I commit every 1000 records. Thanks once again for listening and hope someone can help provide some input James [Non-text portions of this message have been removed]
