Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
"MSSql DB On Windows" pattern is not setting Status (install_status) to installed when discovery identifies that the Instance is properly discovered. - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • "MSSql DB On Windows" pattern is not setting Status (install_status) to installed when discovery identifies that the Instance is properly discovered.
KB0829866

"MSSql DB On Windows" pattern is not setting Status (install_status) to installed when discovery identifies that the Instance is properly discovered.


1816 Views Last updated : Jun 16, 2025 public Copy Permalink
KB Summary by Now Assist

Description

"MSSql DB On Windows" pattern is not setting status (install_status) to installed when discovery identifies that the Instance is properly discovered.

Some cmdb_ci_db_mssql_instance records are left as "Absent".


This is because the pattern is not updating install_status field.

The field is set to default field value "Installed" during the first discovery.

If for any reason the Status field value is changed (e.g. due to deletion strategy, it may be changed to "Absent"), then the following discovery will not change it back to "Installed".


Steps to Reproduce

> Run discovery to a Windows Server that's hosting MS SQL

> Change status of discovered cmdb_ci_db_mssql_instance record to Absent

> Run discovery again to the Windows Server, status of cmdb_ci_db_mssql_instance is still showing Absent

Workaround

The fix is to modify the pattern to update "install_status" field to value "1":

Pattern Designer > MSSql DB On Windows > 
click on "Identification for MS SQL Server" > step 56. Create the main CI > click on plus sign to add an additional field: 
name: install_status, value: 1
Save and publish the pattern.

now go back to MSSql DB On Windows pattern, click on "Identification for MS SQL or TCP with port" > step 27. create the main CI > click on plus sign to add an additional field: 
name: install_status, value: 1
Save and publish the pattern.


Related Problem: PRB1397217

Potentially Seen In

There is no data to report.

Fixed In

Quebec

The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.