To implement GDPR requirements, we need to clean up the database.
There is some underline issues with this process
Problem 1: Cleaning the database with a specific date leads to errors. The following settings are in use for the clean-up:
Delete all tombstoned data Filter options: -> Delete collected data by collection date -> Data collected before a specific date Selected date: xx/xx/xx Error: The conversion of a varchar data type to a date time data type resulted in an out-of-range value.
Problem 2: Clean Database, older than a certain number of days The following settings were used for the clean-up:
Delete all tombstoned data Filter options: -> Delete collected data by collection date -> Data older than a certain number of days. There are no errors here. However, no data is being deleted, even though we expect it to be. We expect that when an AD user is deleted in AD, they should then be marked as "LDM_TOMBSTONED = 1" in all tables Instead, we observe the following: - In the table tblAccount, all records have: LDM_TOMBSTONED = 0 - In the table tblDomainUser, there are records with LDM_TOMBSTONED = 0 and LDM_TOMBSTONED = 1.
You need to be signed in and under a current maintenance contract to view premium knowledge articles.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center