The current design of dropping and recreating the "attrep" staging Tables, then altering them to turn off logging, is causing major issues in a very active environment. We continually get locks on the catalog Tables and if any task takes longer or fails and goes into a long rollback all tasks fail due to catalog locking. For our environment it would be much more efficient if the staging Tables were allocated and truncated for each change cycle. I understand that would mean a change Table per target Table but that would still be more efficient than the continual drop and create of Tables at such a high rate. --- Thank You
