Hi there,
I am just wondering what effect (performance wise) adding a new key to a table would have. The reason is, our client heavily uses the Job Budget Line table, yet a report that they desire would require me to add another key to this table.
A co-worker doesn't want me to do this because he believes the more keys in this particular table (or any heavily used table) will slow down the system. Therefore he doesn't believe its worthwhile for the sake of one report.
Therefore we are both curious in checking if adding keys does effect performance at all, or does it only effect hard disk space, etc?
0
Comments
we have a customer who is complaining about the speed of Navision. On the Item Ledger Entry there are many keys. We want to delete some of these keys to check wether the database will speed up.
One problem : we don't know which keys are necessary and which keys can be deleted without problems. <img border="0" title="" alt="[Frown]" src="images/smiles/icon_sad.gif" /> (
You can see the key-size allowed in the C/front developing manual. I know this answer is not very satisfying, but you should always be aware that Navision is not a system that buckles quickly. So after giving some more thought about wether the key is really necessary try it. If you find the key is slowing the system and you haven’t used it anywhere else delete it again, but I am sure it will not be necessary. :?
RIS Plus, LLC