The following are some examples of statements that call stored procedures. To learn how to create a workload by importing SQL from a stored procedure, see Test Stored Procedures for Scalability.
Database
|
Examples
| |||||||||||||||
Oracle |
Example with parameters:
BEGIN YOUR_PROC(:VAR1,:VAR2); END;
Bind Parameter Settings
Example without parameters:
BEGIN YOUR_PROC2 ( ); END;
| |||||||||||||||
Microsoft SQL Server and SAP |
Example with parameters:
exec YOUR_PROC(@VAR1,@VAR2)
Bind Parameter Settings
Example without parameters:
exec YOUR_PROC2
| |||||||||||||||
IBM DB2, ODBC, and MySQL |
Example with parameters:
call procedure-name (?,?,?,?);
Bind Parameter Settings
Example without parameters:
call procedure-name ();
Note: When using an ODBC connection, the syntax for the statement will follow the syntax for the database, with the exception of the parameters. The parameters within the statement would be "?" and the bind parameters names should be 1,2,3,4...
|
Benchmark Factory allows you to import an Oracle trace files for use during database testing. The following provides Oracle commands that can be used to enable Oracle trace file activity.
Note: Please consult Oracle documentation for current trace file commands.
To turn on and off the trace use the ALTER SESSION command:
alter session
set timed_statistics=true
alter session
set max_dump_file_size=unlimited
alter session set events
'10046 trace name context forever, level 4'
alter session set events
'10046 trace name context off'
To activate a trace you don't have read/write access to:
dbms_system.set_bool_param_in_session(
sid => 55,
serial# => 1222,
parnam => 'timed_statistics',
bval => true)
dbms_system.set_int_param_in_session(
sid => 55,
serial# => 1222,
parnam => 'max_dump_file_size',
intval => 2147483647)
Note: If using a release before Oracle 8, release 8.1.6, these parameters can be changed with ALTER SYSTEM commands.
dbms_support.start_trace_in_session(
sid => 55,
serial => 1222,
waits => true,
binds => true)
dbms_support.stop_trace_in_session(
sid => 55,
serial => 1222)
To create an ODBC trace file
In order to install remote agents through the Benchmark Factory console, you need to turn off the firewall or configure the firewall to allow traffic between the console machine and the agent machine. To allow traffic thru the firewall, enable Windows Management Instrumentation (WMI) and open TCP port 135 on the agent machine.
In addition, after the remote agent is installed, the Benchmark Factory console and the remote agent also communicate through port 4568 (by default). To enable this communication, configure an inbound rule on the console machine and an outbound rule on the agent machine.
Note: The console and remote agent communicate through port 4568 by default. You can change this port number in Edit | Settings | General. Check this setting to ensure you use the specified port number when creating inbound/outbound rules.
Enable Windows Management Instrumentation (WMI) to allow communication between the Benchmark Factory console and the remote agent. The following instructions are applicable to Windows 7. For more information, see http://msdn.microsoft.com/en-us/library/aa822854(v=vs.85).aspx.
To enable WMI (Windows 7)
The Benchmark Factory console uses TCP port 135 to start agents remotely, and port 4568 is used by the console and the agent machine for communication. Create inbound and outbound rules to allow port 135 and port 4568 traffic through the Windows Firewall.
Create Inbound Rule on console machine
Create Inbound Rule on agent machine
Create Outbound Rule on agent machine (if outbound connections are blocked)
If outbound connections are allowed, then no action is required.
Note: In Windows Firewall, outbound connections are set to “Allow” by default.
After enabling WMI and configuring inbound/outbound rules, if you encounter an error while attempting to install a remote agent because you are denied access, try the following.
Add a Registry key (Windows 7, Windows 8)
Open the Registry Editor (regedit.exe).
Caution: Editing your Registry incorrectly can cause serious, system-wide problems. It is advised that you back up your Registry before modifying it.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Conditions d’utilisation Confidentialité Cookie Preference Center