Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 Other Forums
 ClearTrace Support Forum
 ClearTrace does not identify stored procedures cor

Author  Topic 

redhotsly
Starting Member

4 Posts

Posted - 2009-07-13 : 12:46:06
I have a stored proc called hd_incident_insert in my app. In ClearTrace I use the "keyword filter" to filter for this exact name : "hd_incident_insert". I get 15 rows in the ClearTrace query result.

One has a high execution count (160) and the item is named "hd_incident_insert". That one is correct. But there are 14 other results with a low execution count (ranging from 1 to 20) and they all have a name that starts with "EXEC hd_incident_insert" followed by a long list of parameters.

Is there a bug in the code that tries to identify the stored proc names?

This was generated using 10 traces files.

Thanks

graz
Chief SQLTeam Crack Dealer

4149 Posts

Posted - 2009-07-13 : 14:05:03
Are the traces small enough that you could send me one? You can use my username at sqlteam.com.

=================================================
Creating tomorrow's legacy systems today. One crisis at a time.
Go to Top of Page

redhotsly
Starting Member

4 Posts

Posted - 2009-07-13 : 14:14:36
Hi, the traces are not big, but I cannot send them to you because of the confidential information they contain. Is there anything else I could send you to help?
Regards,
Go to Top of Page

graz
Chief SQLTeam Crack Dealer

4149 Posts

Posted - 2009-07-13 : 15:01:56
Email me the raw SQL statement and how it was parsed. You'll also have to tell me whether it was an RPC:Completed event or TSQL.

=================================================
Creating tomorrow's legacy systems today. One crisis at a time.
Go to Top of Page

redhotsly
Starting Member

4 Posts

Posted - 2009-07-13 : 16:30:05
Hi,
It is a RPC:Completed event. I have only included RPC:Completed events in my trace. I cannot send you the actual data because that includes production data in the parameter values. I found the 14 rows in the CTTextData table. Could I send you the values of the NormalizedTextData column for those? You would see how the "normalized" values differ.
Thanks,
Go to Top of Page

graz
Chief SQLTeam Crack Dealer

4149 Posts

Posted - 2009-07-13 : 17:25:26
The only way I can fix the normalization is to see the original SQL and the normalized result. Just seeing the normalized result doesn't help me. If it helps you can change the values in the parameters. I just strip those out anyway.



=================================================
Creating tomorrow's legacy systems today. One crisis at a time.
Go to Top of Page

redhotsly
Starting Member

4 Posts

Posted - 2009-07-13 : 17:41:16
It's interesting that you say that you strip those out since they are not stripped out in my case, which is the problem. I will send you the original SQL (with changed parameter values) by email.
Go to Top of Page
   

- Advertisement -