Removing database instances that no longer exist

[Philip Hulshize]

We have databases MSSql and Oracle so far, where some of the applications create database instances which later go away. The app owners are clearly not going to keep up with reporting these, and requesting them to be decom/deleted, nor do I want them to need to.

Is there a way that I can have discovery remove these databases if they are not discovered?

I tried to set a deleting strategy but it does not appear to work in removing these.

[Thomas Powe]

Depending on how often you run discovery, you could create a Table Cleaner that targets that database table and removes any database where Most Recent Discovery is older than 30 days or something....

[Philip Hulshize]

I would not want to do that. There could be a reason that the record went stale. What I want is to discover a server, and if the pattern finds that a database no longer appears on that device, it would remove it. So, it would 'know' that it was gone, not just remove stale.

[Rahul Priyadars]

Ideally Deletion Strategy should work for Child Cis if both of these conditions occur:

• After you run Discovery with the pattern again.
• Discovery successfully finds the main CI but cannot find the related CI.

Can you show me the setting of ur table- sa_ci_to_pattern for Your DB Instance Strategy.

Regards

RP

[Philip Hulshize]

That is the attached screenshot showing deletion strategy