NAA v12.0 Upgrades: File System 0-CreateSchema Job Taking Longer Than Usual? Here's Why!

Products Access Analyzer Discussions & Questions
,
1

Hey everyone,

If you’ve recently upgraded Netwrix Access Analyzer (formerly Netwrix Enterprise Auditor/StealthAUDIT) from v11.6 to 12.0, and you notice the File System 0-CreateSchema job is taking much longer than you’re used to – don’t worry, you’re not alone, and it’s actually expected.

:light_bulb: What’s going on?

As part of the upgrade from v11.6 to 12.0, there’s a new analysis task “18. Data Migration” on the 0-CreateSchema job that:

  • Moves IDs and metadata from the SA_FSAA_Resources table into new, better-organized tables
  • Cleans up mappings in SA_FSAA_Trustees and SA_FSAA_Gates, filling in any missing values with safe defaults

This process helps lay the groundwork for a cleaner, more efficient system — but in environments with a lot of File System data, it can take 12 hours or more to complete.

:white_check_mark: What should you do?

To let the process run smoothly:

  1. Schedule the File System 0-CreateSchema job (no trigger needed)
  2. Temporarily disable other File System jobs under the Scheduled node
  3. Right-click 0-CreateSchema in the Schedules node and select Run
  4. After it completes, re-enable the other File System jobs

:eyes: Still concerned?

If things feel off or you just want some peace of mind, feel free to open a support ticket via the Netwrix Customer Portal. A Support Engineer will be happy to take a look and make sure everything’s moving along as it should.

Hope this helps – and if anyone else has gone through the upgrade from NAA v11.6 to 12.0 and has tips or feedback, feel free to share below!

2

More information on this can be found in our Help Center here:
Extended Runtime for 0-Create Schema Job Post v12.0 Upgrade