In some environments, software evidence discovered as Integration Services may be reported as SQL Server Integration Services. This can occur when SQL Server Management Studio (SSMS) is installed separately without the SQL Server.

SQL Server Integration Services exists in two forms:

1. The SSIS runtime is a licensed Windows service installed with SQL Server and used to execute ETL packages.
2. The Integration Services component included with SSMS is a development and design tool only and does not require a paid license.

Because these two components may appear similar at discovery time, they can be difficult to distinguish based on software evidence alone, and both may map to SQL Server Integration Services (ID: 23924819). 

Issue details

The SSIS runtime installed with SQL Server runs as a Windows service and is a licensable component.
The Integration Services component included with SSMS does not install a Windows service and is not licensable.

In some cases, both components may be discovered using similar evidence names, such as Integration Services, which can result in the SSMS development tools being reported as the licensed SSIS component. This results in a false positive recognition of the application SQL Server Integration Services (ID: 23924819). 

How this appears in the environment

You may observe this issue when:

• The discovered application name is Integration Services

• SSMS is installed separately on the system.

In contrast, systems with the SSIS runtime installed typically show:

• A discovered name that includes the SQL Server version

• An SSIS Windows service present on the host

Fix status

Evidence of the component with footprint "Integration Services" that is a component of SSMS has been ignored in Technopedia.

Below are some evidence patterns mapped to Microsoft SQL Server Integration Services.

Summary of before-and-after updates for SSIS evidence mapping

Conclusion

The Content Ops team have ignore evidence named “Integration Services” (matching this pattern) in Technopedia, while maintaining the general mapping for “SQL Server Integration Services”.