Is SQL overhead measured in the performance tools or must you use pex and
or the sql components to setup various versions of monitors and such using
iseries access to gather and report on what is taking place on your system.
What is an easy way to drill down to jobs that are using sql on your
system, I have a tool called wrkodbcjob that somewhat gets you your
odbc/jdbc jobs etc.
Using netstat, how can you quickly determine which jobs are using sql and
by what ports, another words how many jobs/users are currently performing
some sort of sql on my box.
Created a new file as a clob, that has ended up clobbering my system cpu,
anyone seen anything like this, all versions of i5/os and it makes no
If your designing applications using client side sql and or embedded sql
what are the performance metrics that should be used to determine that
various amount of remote clients and systems performing various types of
sql against your database should be allowed, is this a
model/cpw/memory/processor type situation that could effect this.
I have been reading the sqe vs the cqe information and it seems that most
of what I have going on is sqe based.