Benchmark Factory allows you to import SQL from a SQL Server trace table. This allows you to replay your database activity with the same timing as was originally captured on an existing in-house SQL Server database application.
The resulting workload contains a user scenario consisting of the sequence of captured SQL transactions.
Before importing SQL from a SQL Server trace table, use SQL Profiler to save the SQL trace as a trace table. See the following topics for more information:
To import a workload from a SQL Server trace table
To jump to the Test Options tab, click Test Options at the bottom of the Summary page. Review the following for more information:
Tab | Description |
---|---|
Transactions tab |
Modify the transactions and the transaction mix for the test. For a custom test, add transactions. |
Options tab | Enable scaling for the user scenario. See Options Tab (Capture/Replay) for more information. |
Timing tab |
User Startup—Select one of the following options:
|
Advanced tab |
Specify Repository options, error handling, and connect/disconnect options for the test. See Advanced Tab for more information. |
Benchmark Factory allows you to import SQL from an ODBC trace file generated by the ODBC Data Source Administrator. This allows you to load test your database using workloads from an existing in-house ODBC database application.
The resulting workload contains a user scenario consisting of the ordered sequence of captured SQL Transactions from the ODBC trace.
See Creating an ODBC Trace File for instructions on how to create an ODBC trace file.
To import an ODBC trace file
To jump to the Test Options tab, click Test Options at the bottom of the Summary page. Review the following for more information:
Tab | Description |
---|---|
Transactions tab |
Modify the transactions and the transaction mix for the test. For a custom test, add transactions. |
Options tab | Enable scaling for the user scenario. See Options Tab (Capture/Replay) for more information. |
Timing tab |
User Startup—Select one of the following options:
|
Advanced tab |
Specify Repository options, error handling, and connect/disconnect options for the test. 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.
Benchmark Factory allows you to create a workload (or add to a workload) by importing SQL from a delimited text file. This allows you to load test your database using workloads from existing in-house generic database applications.
To Import from a Delimited Text File
If you selected Delimited, the Specify Column Delimiter page opens. Select delimiter options.
Note: Only the first 20 rows of the file display.
If you selected Fixed field, the Fixed Field Column Positions page opens. Configure the column or columns.
Note: Only the first 20 rows of the file display.
To jump to the Test Options tab, click Test Options at the bottom of the Summary page. Review the following for more information:
Tab | Description |
---|---|
Transactions tab |
Modify the transactions and the transaction mix for the test. For a custom test, add transactions. |
Options tab | Enable scaling for the user scenario. See Options Tab (Capture/Replay) for more information. |
Timing tab |
User Startup—Select one of the following options:
|
Advanced tab |
Specify Repository options, error handling, and connect/disconnect options for the test. 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.
Benchmark Factory allows you to import SQL from Oracle Dynamic Performance Views. This allows you to import SQL transactions identified by the Oracle for further testing under a load.
The resulting workload is a mixed workload containing either the most-often executed, the most time-consuming, or the most-recently executed SQL transactions.
To import from the Oracle Dynamic Performance Views
Deselect the Include system activity (SYS USER) option to exclude system activity.
Note: It is not recommended to include system activity. Including it imports Oracle SQL statements routinely run by Oracle for maintenance reasons, and is not required for the load testing process.
Or you can select the Test Options tab to modify all test options. Review the following for additional information:
Tab | Description |
---|---|
Transactions tab |
Modify the transactions and the transaction mix for the test. |
User Load tab | Modify the number of users per test iteration. See Specify User Load for more information. |
Timing tab | Specify sampling, pre-sampling, and user start-up times for the test. See Timing Tab for more information. |
Advanced tab |
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.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Termini di utilizzo Privacy Cookie Preference Center