Component Configuration Help - SQL Server User Experience Monitor

I'm not a DBA, but my DBA's gave me a query to run against several SQL databases in our environment that will monitor db file size and fast growth. The SQL Server User Experience Monitor seems to be the perfect component type to use in my template. Let me know if there is a better way (maybe Powershell?).

Looking at the component configuration, it all seems relatively simple, but the "SQL Server Instance" field confuses me a bit. We have tons of SQL servers and instances this template will be applied to. Does this field mean I need to create a component for each and every instance on each SQL server the template will be applied to? The same question may apply to the "Initial Catalog" field.

I was looking to just apply the template to a bunch of SQL servers, and have it automatically apply to every instance on the server. Not a big deal if this isn't possible and a component needs to be created for each instance. I just want to clarify proper usage.

Thanks for your help!

Find more posts tagged with

sql

component settings

sam templates

Accepted answers

All comments

Seashore

If the query you got from your DBA is just for ONE database, you have to apply this to every database on every instance you want to monitor. BUT you don't have to create new templates for every instance.

You can "Override" the fields for instance and database when applied. Setting the vales that applies for that instance and database.

LatteLarry

I think I understand what you're saying. By override, you mean I can edit the assigned template and change the Instance and Catalog fields. Am I right?

Assuming I am following what you're saying, I think that would work. However, what if the server I have the template applied to has more than one Instance? I guess I could just create a duplicate component in the template for each additional instance?

I'm assuming there's no way to use a variable for instance name? The DB will always be master.

Seashore

Hi, you are correct. Apply template and change the fields that need to be changed.

No variables on the instance field.

Say that you on many SQL servers have several instances. You could at the template add a couple of components with different instances. Maybe disable all but one and when applied enable the once you need. So that you apply one template to each server even though it has several instances.