SQL profiler templates- custom vs default

have you seen value in building your profiler templates and keeping for future use or are you satisfied generally with the default ones? if custom, then do you see value in porting it across servers in all situations/circumstances of issues?
LVL 5
25112Asked:
Who is Participating?
 
Vitor MontalvãoConnect With a Mentor MSSQL Senior EngineerCommented:
I never liked the default templates. For all these years working as DBA I already had customized templates.
It must sure that you'll need more than one template so you may use them depending on the issue (long running queries, errors, locks & deadlocks, user connections, ...).
0
 
Nakul VachhrajaniConnect With a Mentor Technical Architect, Capgemini IndiaCommented:
Yes, and yes.

In our development and quality assurance work, we generally use our own custom templates that offer a mix of basic profiling, error capture and performance counters with custom filters so that everyone can have their own view containing only their activity.

For example, we start off from the TSQL_SPs default template, and then add the following events (at least):
Errors and Warnings -> User Error Message
TSQL->SQL:StmntCompleted

We then add a couple of columns, (HostName, Duration, etc) and add filters on it.

That being said, as the product supports newer SQL Server releases, we migrate the templates as well.

So, is there any other question in this regard? Are you facing any issues or just doing some scholarly research?
0
 
25112Author Commented:
we are looking for right standards in this area.. thanks for your input, which helped.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.