
Back in the day ( many days ago ) we were asked to preform Checklinks in Dynamics on a somewhat regular basis.
I have a client from back in those days that is asking if we are still running those processes? I have not been doing as a regular process as I recall reading / being told some time back, that since we are on SQL it is not 'as necessary' and so should only be used when attempting to repair or recreate select tables.
Is that correct?
For that matter, the SQL function on the Application tools page is also a question I have. Of course I have access to SQL Server directly, do I need to have anyone doing anything in the SQL tab??
Just trying to close loose ends - short term memory - very long term forget.......
Hi Bill,
From our perspective in Microsoft Support, we don't generally recommend running Check Links routinely. Only under the following conditions in general: (There can obviously be exceptions to this too and could be reasons the businesses run it routinely like if they have a large number of integrations or customizations that periodically push incorrect data that needs to be corrected)
1. If there is an error or issue in GP that has an article or support blog suggesting that Check Links will fix that error or data condition.
2. If an article or support blog recommends it for a process such as enabling Multicurrency, a year end close (we have an optional item on the list to run check links), or upgrade processes.
3. Like mentioned above, if you have a large number of integrations or customizations that periodically push incorrect data that needs to be corrected.
As for the SQL Maintenance in the User Interface, I cannot think of any routine reason that we would use that. It's most of the time just used in support if there was an issue with upgrading a table or a table gets corrupt so the table and it's stored procedures need to be dropped and recreated after making a backup of the data so it can be inserted back in.
I hope this helps!
Isaac Olson
Microsoft Support