Kostas Dimakis

Vice Admiral
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2010-05-12
15:00
566 views
Dear forum,
I installed my Diag Server 8.04 and a .NET Diag Probe 8.04 on an Application Server (IIS) of my customer.
It works fine and brings all the details about my BPM profiles, server requests, load, tiers, etc.
It also shows me the "SQL Statements" but this is not what I was expecting from these views (see attached).
I was expecting to see the actuall queries (select * from ... etc.) but instead I see something that reminds me of functions (?)
Do I miss anything here?
Should I install a Diag Collector to monitor the DB Server of this application to get this? Would this help at all?
My ct wants to see the SQL queries and I do not know if and what I am missing here.
Thanks in advance,
Kostas
I installed my Diag Server 8.04 and a .NET Diag Probe 8.04 on an Application Server (IIS) of my customer.
It works fine and brings all the details about my BPM profiles, server requests, load, tiers, etc.
It also shows me the "SQL Statements" but this is not what I was expecting from these views (see attached).
I was expecting to see the actuall queries (select * from ... etc.) but instead I see something that reminds me of functions (?)
Do I miss anything here?
Should I install a Diag Collector to monitor the DB Server of this application to get this? Would this help at all?
My ct wants to see the SQL queries and I do not know if and what I am missing here.
Thanks in advance,
Kostas
1 Solution
Accepted Solutions


Cadet 1st Class
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2010-05-12
18:24
Looks like what you guys are seeing is SQL Stored Procedure (SP) names. Your DBA's should be able to tell you what SQL statement makes up the particular SP's.
I have the same issue (but it's not really an issue) for some of my .NET applications. As far as I know, there's no way to instruct Diagnostics to give you the SQL included in the SP. You have to remember that Diagnostics .NET Probe sees things from the applications perspective -- and if the application is calling a SQL SP, that's all it will see.
Hope this helps.
I have the same issue (but it's not really an issue) for some of my .NET applications. As far as I know, there's no way to instruct Diagnostics to give you the SQL included in the SP. You have to remember that Diagnostics .NET Probe sees things from the applications perspective -- and if the application is calling a SQL SP, that's all it will see.
Hope this helps.
3 Replies
parkar

Fleet Admiral
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2010-05-12
17:17
Hi Kostas,
I am also facing the same
It also shows me the "SQL Statements" but no queries
I was also expecting to see the actuall queries (select * from ... etc.) but instead I see something that reminds me of functions
Any one can suggest really appreciated
Cheers
Cheers!
Nvr Blame a day in ur life....... Good day gives "happiness" & Bad day gives "experience" ......
Nvr Blame a day in ur life....... Good day gives "happiness" & Bad day gives "experience" ......


Cadet 1st Class
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2010-05-12
18:24
Looks like what you guys are seeing is SQL Stored Procedure (SP) names. Your DBA's should be able to tell you what SQL statement makes up the particular SP's.
I have the same issue (but it's not really an issue) for some of my .NET applications. As far as I know, there's no way to instruct Diagnostics to give you the SQL included in the SP. You have to remember that Diagnostics .NET Probe sees things from the applications perspective -- and if the application is calling a SQL SP, that's all it will see.
Hope this helps.
I have the same issue (but it's not really an issue) for some of my .NET applications. As far as I know, there's no way to instruct Diagnostics to give you the SQL included in the SP. You have to remember that Diagnostics .NET Probe sees things from the applications perspective -- and if the application is calling a SQL SP, that's all it will see.
Hope this helps.
Kostas Dimakis

Vice Admiral
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2010-05-13
20:20
Thanks Dave. This was my case. I verified it with the DBAs.
Thanks.
Thanks.