How to stop Operational status changing from Dr Standby on discovery of SQL Instances

Richard Nelson · 3 weeks ago

Hi Folks, we have a need to prevent the Operational Status on an MS SQL Instance being updated when the device is discovered.

We put our DR SQL instances into the 'DR Standby' status so we can easily identify them. However discovery is designed to pop them back into the Operational status which is causing issues for some internal processes.

Does anyone know of an easy and reversible method of disabling this functionality?

Thanks

sivasankaris · 2 weeks ago

Hi @Richard Nelson , Operational status field is populated by MS SQL pattern which is triggered. You may Go through this pattern and disable that particular step which updates the operational status.. This solution is temporary, you have to revert it back after some time because it will affect all other MS SQL Apps operational status.. Or else you may customize this operational status update according to your needs.. This will works correctly..

If this is helpful.. Please Mark it as helpful and please Accept My Solution...

Best Regards,

SIVASANKARI S

View solution in original post

sivasankaris · 2 weeks ago

Hi @Richard Nelson , Operational status field is populated by MS SQL pattern which is triggered. You may Go through this pattern and disable that particular step which updates the operational status.. This solution is temporary, you have to revert it back after some time because it will affect all other MS SQL Apps operational status.. Or else you may customize this operational status update according to your needs.. This will works correctly..

If this is helpful.. Please Mark it as helpful and please Accept My Solution...

Best Regards,

SIVASANKARI S

David77 · 2 weeks ago

Not sure if this would work, but have you looked at using IRE rules?