Hi Robert, 

Would you be able to provide some examples of issue that might be encountered if table audits are not turned off? 

Also, is there a way to turn off the audits after the data has been extracted and copied over to the new server? [ in SQL or ?] 

Thank you

I only figured it out because the sequencing monitor wasn't moving and I put a profiler trace on it.  This is when I found that it was creating all of those AUDITH records.  The only issue that it causes is a huge waste of time, and you can turn it back on after you have finished with your migration.

Hi, What method do you use to disable and then re-enable all the table and field audits? did you created an sql server script? if so, can you share it? Regards.

I went into the Tables function, found the table record that had it enabled, and disabled it by deselecting the options under the audit tab, and before doing a forced validation on the table.

And an easy way to find them is by going into SQL to run a query.  

select Distinct TBL_0 from PROD.AUDITH

In 2013 I did a presentation at a Sage Summit and gave the following query. You can download all the queries and bonus scripts from this blog post. Hope t helps. 

https://www.sagecity.com/support_communities/sage_erp_x3/b/sageerp_x3_product_support_blog/posts/sage-summit-c-139-prepare-for-inifitiy-and-beyond

SELECT

  TBL_0,

  COUNT(TBL_0) TableCount,

  EVT_0,

  COUNT(EVT_0) EventTypeCount

FROM SEED.AUDITH

GROUP BY TBL_0, EVT_0

ORDER BY COUNT(TBL_0) DESC, COUNT(EVT_0) DESC

Hey, Bob!  Long time no speak!  I hope you are doing well?!

Good thanks, hope the same for you.