Our users are forced to run batch jobs. These kinds of jobs run for several hours on the users client. During this the client executes some expensive query's, query's with tens of thousands of executions, heavy on read and writes and most have a execution time above 100ms.
It would be very useful that once we have identified query's and we know which batch job they belong to we can group or give these query's the same name. This way it's more clear what functionality within the software is most likely to be the cause of potential performance issues.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community.
More than 150,000 members are here to solve problems, share technology and best practices, and directly
contribute to our product development process.