record RENAME seems to process totally unrelated tables

Toddy_Boy

Hi all

For starters we have a heavily customized database, SQL Server, Client 2009 objects 2.01.B

I'm trying to get an understanding as to what Navision is doing when renaming a record. In our strangest scenario, if we rename a Site, Navision shows some very random messages about updating tables that have no relation to the Site table whatsoever, e.g. Holiday Requests, Priority both of which are new customized tables with no relation to the site table.

The knock on effect is that this operation has to be done out of hours due to the length of time it takes to perform on a site rename.

I appreciate it's another needle in a haystack time but any pointers are as always appreciated.

ara3n

When you rename, Nav doesn't know all the table that it relates to. So it goes through all of the table to see if there is a relationship. After the first run I believe it keeps it in cache so that second rename is faster.

MBerger

Sometimes, and only if you are REALLY sure the table you are renaming is not connected to any other table ( i mean, that it's not used as a tabelrelation anywhere ), it more efficient to delete and then re-insert your record, instead of using a rename.

Toddy_Boy

ar3an - do you know if this would stay cached on the local machine indefinitely or whether the caching will be available for everyone?

MBerger - it's referenced in a number of places so this is sadly a non-starter

as always, thanks for the pointers

David_Singleton

Toddy Boy wrote:

I'm trying to get an understanding as to what Navision is doing when renaming a record. In our strangest scenario, if we rename a Site, Navision shows some very random messages about updating tables that have no relation to the Site table whatsoever, e.g. Holiday Requests, Priority both of which are new customized tables with no relation to the site table.

Make sure you have keys (indexed) on the linked fields in the tables with a lot of records.
In reality though Rename should be very rarely used, and only for exceptions and fixing errors. If you find yourself using it a lot, then either you need to redesign your way of working/data model or need to train the users to make less errors.

dans

David Singleton wrote:

Make sure you have keys (indexed) on the linked fields in the tables with a lot of records.
In reality though Rename should be very rarely used, and only for exceptions and fixing errors. If you find yourself using it a lot, then either you need to redesign your way of working/data model or need to train the users to make less errors.

:thumbsup:

FDickschat

Make sure your clients object cache is set to an appropriate value. I usually set it to 100MB. This speeds up renaming a lot.