I already have a working workbench. What i am trying to do is consolidate the
number of requests that i am using. from say 50 to 10 (with randomly
generated variables.) The purpose of the test is to get as close to
live/realistic environment as possible. People are performing all kinds of
different searches with different criteria everytime.
So in an effor to replicate the dynamic environment i need to create a
series of JDBC requests that (evolve) with every iteration.
pool: ${pool}
statement: select ${col1} from ${table} where ${col2} = '${value}'
So is that how JMeter recognizes a variable? and if that is the case then
would i have to create a file with all the different types of search
criteria needed to fill those values?
Also, i hear what you are saying about the elements and how they allow the
JDBC request to establish the connecting to the DB. That part im good on.
Because what i can do is create all the elements i need to connect to the
multiple databases with the (evolving) JDBC requests in the associated
pools that i need them in.
Thank you though for getting back to me so quickly. It is greatly
appreciated.
Regards,
[EMAIL PROTECTED]
sebb-2 wrote:
>
> On 12/10/2007, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>>
>> Hey,
>>
>> I stated this in another post but decided to create my own for tracking
>> purposes.
>> My current setup is as such,
>>
>> 3+ Thread groups
>
> Why use multiple thread groups?
>
>> 3+ JDBC Connection Elements
>
>> Runtimers
>> Loop Timers
>> and 45 individual JDBC Requests.
>>
>> The reason i am looking for a method of creating an alternating JDBC
>> request
>> becomes obviouse as constantly having to come up with unique searchs
>> becomes
>> more and more combersome and time consuming.
>
> Alternating implies repetition (e.g. 1,2,3,1,2,3) but then you mention
> unique - which do you mean? Or do you mean variable request?
>
>> With 5 JDBC requests configured to have alternating values i could
>> constantly have changing searches and never have an instance or a cached
>> search happening and thus contaminating my results. problem is i do not
>> know
>> how to create the said JDBC request.
>>
>> Is it also possible to have an element alternate between different
>> databases
>> without having to creat an entirely new element/thread group?
>
> You need 1 pool for each unique set of connection attributes (database
> name, driver, username etc)
>
> The JDBC request uses the pool name to get the database connection;
> the pool name can be a variable, and the SQL statement can use
> variables as well.
>
> e.g. JDBC sampler:
>
> pool: ${pool}
>
> statement: select ${col1} from ${table} where ${col2} = '${value}'
>
> You may also be able to use a prepared statement with the appropriate
> values.
>
>> I am not a coder and would need a pretty good run down of how to perform
>> that kind of action. Still very new to the coding arena.
>
> JMeter does not require "coding" but like any test application you
> need to read the manual (probably a few times).
>
> Equally importantly, you need a good understanding of the system you
> are testing and particularly what you are trying to achieve by
> running the tests.
>
>
>> regards,
>> [EMAIL PROTECTED]
>> --
>> View this message in context:
>> http://www.nabble.com/JDBC-requests-with-alternating-variables-tf4614204.html#a13177071
>> Sent from the JMeter - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/JDBC-requests-with-alternating-variables-tf4614204.html#a13214333
Sent from the JMeter - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
