 | |
#1
 
| |||
| |||
|
detecting table scans -
11-21-2008
, 06:26 AM
#2
| |||
| |||
|
|
Hello, In a huge complex Sybase application written in ESQL/C and JDBC with hundreds of tables and some hundred concurrent connects to ASE 12.5.4 we're facingsituations in which a simple FETCH from a small table, which normally takes 5-6 ms, takes from time to time 10-20 ms, or INSERT lasts even 3 secs; it is unclear what is causing this. One of our hypothesis is that the application in some areas, sometimes, is falling into full table scans, and the above mentioned long INSERT is victim of such an event of other processes running at the same time. My question is: Is there some kind of logging I could switch on (for example by a trace flag) which will let ASE log all such table scans? TIA * * * * matthias --http://www.unixarea.de/ |
monSysSQLText?
-bret
#3
| |||
| |||
|
|
Hello, In a huge complex Sybase application written in ESQL/C and JDBC with hundreds of tables and some hundred concurrent connects to ASE 12.5.4 we're facingsituations in which a simple FETCH from a small table, which normally takes 5-6 ms, takes from time to time 10-20 ms, or INSERT lasts even 3 secs; it is unclear what is causing this. One of our hypothesis is that the application in some areas, sometimes, is falling into full table scans, and the above mentioned long INSERT is victim of such an event of other processes running at the same time. My question is: Is there some kind of logging I could switch on (for example by a trace flag) which will let ASE log all such table scans? TIA * * * * matthias --http://www.unixarea.de/ |
monSysSQLText?
-bret
#4
| |||
| |||
|
|
Hello, In a huge complex Sybase application written in ESQL/C and JDBC with hundreds of tables and some hundred concurrent connects to ASE 12.5.4 we're facingsituations in which a simple FETCH from a small table, which normally takes 5-6 ms, takes from time to time 10-20 ms, or INSERT lasts even 3 secs; it is unclear what is causing this. One of our hypothesis is that the application in some areas, sometimes, is falling into full table scans, and the above mentioned long INSERT is victim of such an event of other processes running at the same time. My question is: Is there some kind of logging I could switch on (for example by a trace flag) which will let ASE log all such table scans? TIA * * * * matthias --http://www.unixarea.de/ |
monSysSQLText?
-bret
#5
| |||
| |||
|
|
Hello, In a huge complex Sybase application written in ESQL/C and JDBC with hundreds of tables and some hundred concurrent connects to ASE 12.5.4 we're facingsituations in which a simple FETCH from a small table, which normally takes 5-6 ms, takes from time to time 10-20 ms, or INSERT lasts even 3 secs; it is unclear what is causing this. One of our hypothesis is that the application in some areas, sometimes, is falling into full table scans, and the above mentioned long INSERT is victim of such an event of other processes running at the same time. My question is: Is there some kind of logging I could switch on (for example by a trace flag) which will let ASE log all such table scans? TIA * * * * matthias --http://www.unixarea.de/ |
monSysSQLText?
-bret
#6
| |||
| |||
|
|
Hello, In a huge complex Sybase application written in ESQL/C and JDBC with hundreds of tables and some hundred concurrent connects to ASE 12.5.4 we're facingsituations in which a simple FETCH from a small table, which normally takes 5-6 ms, takes from time to time 10-20 ms, or INSERT lasts even 3 secs; it is unclear what is causing this. One of our hypothesis is that the application in some areas, sometimes, is falling into full table scans, and the above mentioned long INSERT is victim of such an event of other processes running at the same time. My question is: Is there some kind of logging I could switch on (for example by a trace flag) which will let ASE log all such table scans? TIA * * * * matthias --http://www.unixarea.de/ |
monSysSQLText?
-bret
#7
| |||
| |||
|
|
Hello, In a huge complex Sybase application written in ESQL/C and JDBC with hundreds of tables and some hundred concurrent connects to ASE 12.5.4 we're facingsituations in which a simple FETCH from a small table, which normally takes 5-6 ms, takes from time to time 10-20 ms, or INSERT lasts even 3 secs; it is unclear what is causing this. One of our hypothesis is that the application in some areas, sometimes, is falling into full table scans, and the above mentioned long INSERT is victim of such an event of other processes running at the same time. My question is: Is there some kind of logging I could switch on (for example by a trace flag) which will let ASE log all such table scans? TIA * * * * matthias --http://www.unixarea.de/ |
monSysSQLText?
-bret
#8
| |||
| |||
|
|
Hello, In a huge complex Sybase application written in ESQL/C and JDBC with hundreds of tables and some hundred concurrent connects to ASE 12.5.4 we're facingsituations in which a simple FETCH from a small table, which normally takes 5-6 ms, takes from time to time 10-20 ms, or INSERT lasts even 3 secs; it is unclear what is causing this. One of our hypothesis is that the application in some areas, sometimes, is falling into full table scans, and the above mentioned long INSERT is victim of such an event of other processes running at the same time. My question is: Is there some kind of logging I could switch on (for example by a trace flag) which will let ASE log all such table scans? TIA * * * * matthias --http://www.unixarea.de/ |
monSysSQLText?
-bret
#9
| |||
| |||
|
|
Hello, In a huge complex Sybase application written in ESQL/C and JDBC with hundreds of tables and some hundred concurrent connects to ASE 12.5.4 we're facingsituations in which a simple FETCH from a small table, which normally takes 5-6 ms, takes from time to time 10-20 ms, or INSERT lasts even 3 secs; it is unclear what is causing this. One of our hypothesis is that the application in some areas, sometimes, is falling into full table scans, and the above mentioned long INSERT is victim of such an event of other processes running at the same time. My question is: Is there some kind of logging I could switch on (for example by a trace flag) which will let ASE log all such table scans? TIA * * * * matthias --http://www.unixarea.de/ |
monSysSQLText?
-bret
 |
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.