You are hereDatabase Script Development

Database Script Development


  • No struggling with database concepts or protocol selection common with other providers
  • Hardened scripts which accurately represent the nature of the query to the system
  • Less time required per script which allows for a larger number of scripts created within your script development window.

Database script developers are mandated to understand the foundations of the relational database before being allowed to develop database scripts. Our script developers understand the differences between queries and stored procedures. They possess an architectural view of systems which allows for the creation of database virtual users even in the absence of a front-end client, so long as the queries or stored procedure calls are known.

The above is in stark contrast to most organizations professing skills in the development of database virtual user scripts for LoadRunner. Instead of employing an individual with database skills in place before being educated on the use of LoadRunner, organizations use the greenest of individuals to build scripts. These individuals are typically just out of school, using QA as an entry point ot an organization before moving onto development or project management. Such organizations are not able to develop the depth of skills required to be successful with database virtual users.

Below you will find characteristics associated with our scripts. Are you certain that all of your scripts incorporate the best practices noted below? Send us a script for review and we'll match your script up to the list and provide to you a report of any deviations from the best practices.


All of our database virtual user scripts include the following

  • Clear and concise comments
  • Full parameterization of user entered portions of queries
  • Handling of session specific data
  • Collection and resubmission of data between client and server appropriate to the business process
  • Timing record (transaction) inclusion matched to your requirements and specifications
  • Pacing matched to your load model
  • Varying think time representing user behavior
  • Checking for expected return data
  • Handling of error conditions
  • Efficient use of resources by the virtual user to allow for maximal use of Load Generators without becoming resource bound on the load generators