Extended Runtime for 0-Create Schema Job Post v12.0 Upgrade
Symptom
After upgrading Netwrix Access Analyzer (formerly Enterprise Auditor) from v11.6 to v12.0, the File System 0-Create Schema job requires significantly more time to complete.
Cause
When upgrading Access Analyzer from v11.6 to v12.0, the File System 0-Create Schema job is expected to take longer than it has in previous versions. Analysis task 18. Data Migration is moving IDs and metadata from the SA_FSAA_Resources table into separate, more organized tables, then removing the original columns. It also fixes table mappings for SA_FSAA_Trustees and SA_FSAA_Gates by replacing missing values with default values if they have not been filled yet. For large environments, or environments with large amounts of File System data, this can take 12 or more hours.
Resolution
- Schedule the File System
0-Create Schemajob (no trigger needed). - Disable all other File System jobs in the Schedules node.
- From the Schedules node, right-click the
0-Create Schematask and select Run. - Once the
0-Create Schemajob has completed, re-enable all other File System tasks.
IMPORTANT: If the job runs for more than 24 hours, then proceed with the following steps:
- Stop the task.
- Close the console.
- Run the following commands on the SQL database:
-
ALTER TABLE SA_FSAA_ResourcesScanTypeDetails NOCHECK CONSTRAINT ALL
-
ALTER TABLE SA_FSAA_ResourceMap NOCHECK CONSTRAINT ALL
-
- Once the above commands complete successfully, run the
0-Create Schematask. - Once the job completes, run the following commands:
-
ALTER TABLE SA_FSAA_ResourcesScanTypeDetails WITH CHECK CHECK CONSTRAINT ALL
-
ALTER TABLE SA_FSAA_ResourceMap WITH CHECK CHECK CONSTRAINT ALL
-