SQLBigEyes Hammer (Freeware)

• Run/Stop multiple hammer windows simultaneously
• Support for MySQL/MariaDB (Beta)

• Setting execution properties (Repetition count, Thread count, Sleep time, etc.)
• Real-time output of execution performance by thread
• Uninterrupted execution in case of failure by thread
• Saving and reusing Hammer configuration information

• Performance counter support (Windows only)

• Support for query lengths of more than 8000 characters
• Automatic saving/restore of last connection information (except password)

When you open the “New Query” window later, the server connection information set here is applied by default.

Ref-1. Authentication method and account information can be changed in individual Hammer windows.
Ref-2. MySQL/MariaDB support is still in the testing phase (Beta).

Note) SQLBigEyes Hammer supports entering queries of more than 8,000 characters (over).

Note) You can adjust the “Font size” by using the [Ctrl+Mouse Wheel].

• Enter the database to connect to in the [Database] Then set properties on how often and how many times we want to run the query.
• [# of Iterations] is the number of query iterations.
• [# of Threads] is the number of threads to be executed at the same time.
• [Sleep(ms)] can specify the number of milliseconds to wait between repetitions (0 is no wait).

If you want to execute a specific query among several queries, select the query and click the [Run] button.

Caution.

1) In the case of /* */ comments spanning multiple lines, an error occurs, so remove them in advance or change them by line.

2) Lines beginning with -– comments are automatically excluded when executed.

Important. Specifying this option can affect the overall execution time due to additional behavior in the SQLBigEyes Hammer program itself.

(Current Iteration) and (Total Elapsed Time) at the top of the Query window show the accumulated number of iterations and total execution time to date regardless of this option.

[Statitistics-Chart] Tab

[Statitistics-Grid] Tab

After execution is complete, you can see the average execution time and average elapsed time of individual threads in the (Average) row at the bottom.

Tip. Utilize when testing in a redundant environment

SQLBigEyes Hammer is developed so that even if an error occurs during execution, the query continues to be repeated until the specified number of iterations is met. This can be useful when testing Failover behavior in a redundant environment such as Failover Cluster, Always on availability group, auto failover group on Azure, etc

[Options – Fetch Rows & View Result]

Hammer does not process query result rows by default. By specifying the [Fetch Rows] option, you can specify that the default behavior of populating a variable is for the entire result row and for individual column values. This allows you to perform a load test (similar to the actual situation), including the amount of time the client processes data.

In addition, if you select the [View Result] option, the result is displayed in the “Result of Query” tab at the bottom. If the Iterations value is 2 or more, the execution result is displayed in the form of being added to the Grid. The “Iteration” column value indicates the number of iterations.

[Options – Connection Pooling]

Connection using Connection Pooling in ADO.NET (.NET Data Provider), ADO (OLEDB), etc. is the default operation, but if necessary, you can disable the option and perform a load test with Non-Connection Pooling.

It is recommended to use Windows Performance Monitor (Perfmon.exe) to check the overall performance of the current server. You can also use SQL Server Profiler (Trace) or Extended Event to check the performance of individual queries (CPU, Read, Write).

SQLBigEyes Hammer provides the [Performance Monitor] window so that you can check some performance counters simply as shown in the figure. Currently, Batch Requests/sec value is supported, and additional support is planned as needed in the future.

Note) This function is currently being tested (Beta). There may be a delay in the output of the chart when the load of the program itself increases or the computer in use is under load.

Using [Save Configuration] menu, toolbar, or shortcut key, and designate folder and file name to save. The xml file can also be edited directly using an editor tool such as Notepad.

When reusing the saved xml file, select the [Open Hammer] menu and specify the file, a new Hammer window is created, and the query and property information are automatically set.

• For production environment, execute SQLBigEyes Hammer on a separate computer independent from SQL Server.
• If you designate too many threads (more than a few thousand) in one Hammer window, a problem may occur in program execution, so consider increasing it from a small number or executing several other Hammer windows or SQLBigEyes Hammer programs. .
• If you run a query that runs for a very long time, closing the Hammer window may not terminate the query. You need to exit the SQLBigEyes program itself.
• Even if individual queries are very slow or under heavy load, it can cause problems with program execution, so please consider them.

And you can click the [Continue (C)] button to proceed with the operation.

http://www.sqlroad.com/

In addition, technical inquiries and information about SQL Server are handled, so it will be helpful if you use them.

SQLRoad (www.sqlroad.com)