1.1 Updates and Breaking Changes

1.1.1 New Views

The following views have been added to support historic and baseline scan data:

  • srs.previous_fs_scandata

  • srs.previous_fs_scandata_ad

  • srs.previous_fs_scandata_edir

  • srs.previous_fs_scans

  • srs.previous_ncp_trustees

  • srs.previous_ntfs_aces

  • srs.previous_permissions_scans

  • srs.baseline_fs_scandata

  • srs.baseline_fs_scandata_ad

  • srs.baseline_fs_scandata_edir

  • srs.baseline_fs_scans

  • srs.baseline_ncp_trustees

  • srs.baseline_ntfs_aces

  • srs.baseline_permissions_scans

1.1.2 Deprecated Column is_valid

The column is_valid in the table srs.scans and the views srs.current_fs_scans and srs.current_permissions_scans is now deprecated. This column is redundant in that it reflects whether the progress_status column contains the value 4, indicating whether a scan is Current. Since the progress_status column maintains the scan state for the Current, Previous, and Retained scan statuses as well as other scan states, it should be used instead.

This field still remains in the schema for this release, but may be removed in a later version. Note that this column was not added to the new previous_* and baseline_* views.

1.1.3 Deprecated Active Views

The srs.active_* views are now considered deprecated, although they will continue to work with existing Custom Query reports that make use of them at this time.

Each of these views can now be referenced using the equivalent srs.current_* name:

Table 1-1 Deprecated Active Views

Deprecated View

New View

srs.active_fs_scans

srs.current_fs_scans

srs.active_fs_scandata

srs.current_fs_scandata

srs.active_fs_scandata_ad

srs.current_fs_scandata_ad

srs.active_fs_scandata_edir

srs.current_fs_scandata_edir

srs.active_permissions_scans

srs.current_permissions_scans

srs.active_ncp_trustees

srs.current_ncp_trustees

srs.active_ntfs_aces

srs.current_ntfs_aces

NOTE:Although the srs.active_* views still work for this release, they will most likely be removed at a future date.