The SQL Scalability test allows you to execute SQL statements, allowing users to spot potential issues not seen with a single execution. Users can run variations of a SQL statement in order to find the SQL that will perform the best under a load test.
Use this procedure to create a new SQL Scalability test or a Custom Scalability test.
To create a SQL Scalability Test
Or you can select the Test Options tab to modify all test options. Review the following for additional information:
Add transactions for the test.
|User Load tab||Modify the number of users per test iteration. See Specify User Load for more information.|
Execute By—Select one of the following options:
User Startup—Select one of the following options:
Specify Repository options, error handling, and database checkpoints for the test.
You can also specify a file to execute at the beginning or end of each iteration. See Advanced Tab for more information.
After specifying options for this test, you can add another test to the job, configure job setup options, save and close the job, run the job, or schedule the job. For more information about each of these steps, see Quickstart: Create a New Job.
The Create/Delete Benchmark Objects step creates or clears the database objects (tables/indexes, etc.) needed to run industry standard benchmarks. The step is included when you create an Industry Standard Benchmark Test. You can also add the step to an existing workload through the Edit Job Wizard.
Note: To create, delete, and modify database tables/indexes you must have the user login rights required.
To add a Create/Delete Benchmark Objects Test to a Workload
|Create/Load objects if objects don't exist (no backup sets created)||
If objects do not exist, Benchmark Factory creates the objects and loads data.
If you select this option, Benchmark Factory does not create backup tables.
|Delete benchmark objects after completion of job||Benchmark Factory deletes objects after a job is finished.|
|Refresh data using backup sets||
When backup sets exist, Benchmark Factory reloads data and recreates indexes.
If backup sets do not exist, Benchmark Factory creates objects and loads data. Then Benchmark Factory creates the backup tables.
|Recreate objects and reload data every execution||
Benchmark Factory always deletes the existing objects and then recreates/reloads for each job execution.
This allows you to ensure that the dataset is always in initialized status.
|Refresh data using inserts||
If data does not exist, Benchmark Factory uses bulk insert to load data.
If the following Benchmark Settings are selected,
and the Benchmark Scale factor of the existing tables does not match the new requirement, the process of inserting additional data or deleting data my run long, depending on the size of the existing data and number of indexes.
Note: If database does not support bulk insert, insert is used.
Note: The test is added to the top of the workload list. To move the test down (or up) in the list, right-click the test and select Move Down (or Move Up).
Tip: You can specify a default setting for Object/Data Retention in Edit | Settings | Benchmarks.
You might want to add an executable file (.bat or .exe) as part of a job. This gives you the flexibility to set up your database before running a workload. For example, you could run a .bat file to set up a prepared SQL statement before running a workload.
To add an Execute File step to a workload
To add a timeout, select the Enforce Timeout option and enter the number of seconds for Benchmark Factory to wait for the execution to complete before continuing the job.
You can specify a default setting for this option in Edit | Settings | Execute File.