![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
#3
| |||
| |||
|
#4
| |||
| |||
|
|
I was hoping somebody could answer this one way or another. I am relatively new to Ingres coming from MS SQLServer. One of the extremely useful things I used to be able to do in SQLServer was to trace (profile) all SQL running on the server using a utility called profiler. In the profiler I could then filter out SQL coming from particular nodes or users, how long they ran etc etc. The main reason for doing this is that it allowed tuning of SQL independently of the application sending the SQL. The raw SQL and timings could be sent to a table and queried for things like 'the top 5 worst performing queries' or 'how many times' a particular piece of SQL was running. O.K., here is my question. Is there technique in Ingres that can be used to do a similar thing? Most of the connections in my new job here are via JDBC. I would just like to know so that I don't continue chasing something which Ingres can't do in the first place. ------------------------------------------------------------------- For better; or for worse, these are my thoughts. |
#5
| |||
| |||
|
|
I was hoping somebody could answer this one way or another. I am relatively new to Ingres coming from MS SQLServer. One of the extremely useful things I used to be able to do in SQLServer was to trace (profile) all SQL running on the server using a utility called profiler. In the profiler I could then filter out SQL coming from particular nodes or users, how long they ran etc etc. The main reason for doing this is that it allowed tuning of SQL independently of the application sending the SQL. The raw SQL and timings could be sent to a table and queried for things like 'the top 5 worst performing queries' or 'how many times' a particular piece of SQL was running. O.K., here is my question. Is there technique in Ingres that can be used to do a similar thing? Most of the connections in my new job here are via JDBC. I would just like to know so that I don't continue chasing something which Ingres can't do in the first place. |
#6
| |||
| |||
|
#7
| |||
| |||
|
|
Hello, it would be worth checking 'Dynamic Playback - Ingres Community Wiki' (http://community.ingres.com/wiki/Dynamic_Playback) This project was designed initially to replay the queries, but it may give also some hints about the query performance. Unfortunately big pain is, we do not see, when a query completes. Currently we see only when the query is being started. |
![]() |
| Thread Tools | |
| Display Modes | |
| |