How to measure SQL hits due to my application
Use case:
I'm working on a form in development environment and everything works fine. aqPerformance tells me everything is quick. I make a change in my form. aqPerformance still tells me ever...
Forum Discussion
I'm not sure whether or not there exists any sort of SQL profiler integration in TestComplete. So, if anything, you would need to automate interacting with the profiler tool itself.
AQTime, however, might have the ability of doing these kinds of profiling tasks and it DOES integrate with TestComplete.
Check out https://support.smartbear.com/testcomplete/docs/working-with/integration/aqtime/index.html
I've had a quick look at it - and attended AQTime training academy 101 :smileytongue: I can see that it would allow me to look at performance on a global scale. It's big on the application side, but I don't see much on the SQL side. I can't see any indication that it would be able to do someting like error my test if SQL performs more than X queries between the button click and the page being ready after the click. Any experience that would confirm or deny my limited exposure to help me decide if I should use AQTime or write some sort of custom server side profiling scripts (I've got an idea involving stored procedures, xml files,SQL built-in functions and a touch of roasted fennel to make that work...). I'd prefer the former, but would be prepared to do the latter. I just need input before I go and do redo something TC/AQTime can already do
There is an AQTime community
https://community.smartbear.com/t5/AQtime/ct-p/AQTime
Perhaps ask there?
You are welcome to set a performance counter on litterally hundreded of different database based profilers in TestComplete, from connections to latency to commits, etc...
choose Performance counters and select Custom Profilers, go down the list and see the hundreds of different profilers available for SQL Server that are running on your Machine.
I also use Red Gate SQL Profilers, they are very good with great User Interface
AQTime, will do the job as well, I have used it in the past to do SQL Profiling but it is not as easy to use as Red Gate SQL profiler.
Cheers
-Lino
Thanks, I'll ask. I'm just genuinely surprised that nobody else has wanted to measure this in the middle of test runs :smileysurprised:
Just putting in a timer checkpoint can't tell me if a code change is going to kill a SQL server with redundant/multiple calls to the database. Our application by neccesity has to share a SQL server with other applications and there are too many instances of "Your software made all our other software break" to ignore this.
