Prior to releasing a Service Manager implementation for production use, I like to perform some load testing to see how it is performing. During the development phase of a Service Manager deployment it is easy to forget about performance testing. While you are in there working on your own everything is running smooth. Then you move into production and notice you seem to have some performance issues and bottle necks. In order to simulate the load that a production Service Manager environment may experience, I have created a PowerShell script that creates random incidents.


Using this script I am able to test the Service Manager environment while it is under a load. While the script is running I will manually enter and update incidents in the console to see how it performs. On top of that I will use from SQL scripts to watch the delay time for the workflows. These scripts were written by Travis Wright and can be found in his blog Troubleshooting Workflow Performance and Delays ( His script SubscriptionStatus.sql can be used during this simulated load to see if you have any workflow that could cause performance issues for you.


To run the script just need to enter the number of incidents you want to create and the time delay (in seconds) between creating them. Once you enter this information, just execute the script.



The script will create an incident with the title “Load Test Number” and the description “Test please ignore.” It will set a random Classification Category, Urgency, Impact, Support Group, and Incident Source based on the values in your environment.


This script requires that the computer executing it has SMLets installed.


You can either copy the full script text below or click here to download a copy.