harm in overlinking hosts with templates?

[terry]

Hello,

Is there any harm in linking templates to hosts that you know don't have the services the template offers? The reason I do this is to keep the number of discovery actions to a minimum. For example, I have a discovery action for windows hosts. That action links in SQL, Exchange, Open Manage, Windows, etc. However, not all of my hosts have SQL for example. I see that the items view will show stuff like this:
SQL Analysis Services: No such service (255)

These "errors" in the items view don't bother me because triggers will be more granular. This simplifies the host setup process but I don't want to hammer the database with unnecessary stuff either because my implementation is going to be pretty big (>500 hosts). Thoughts?

[terry]

Well, it appears that some items/triggers get fired if you just glob everything in. However, there may be ways around this.

For example, if I just throw in the SQL Server template and SQL services do not exist on the box, the item for service_state will return 255. The trigger is configured to fire if the output is NOT 0 (zero). I modified this to be fire if the output is not 0 or 255 (no such service):
({Template_Microsoft_SQLServer_2005:service_state[ReportServer].last(0)}#0)&({Template_Microsoft_SQLServer_2005:s ervice_state[ReportServer].last(0)}#255)

Anyone see any problems with this way of doing things?

[terry]

Anyone else doing something similar with templates?