Application Performance w/ Microsoft SQL 2025

[Curt Malicoat]

I was curious is anyone has seen any performance hits when using your application with a Microsoft SQL 2025 instance? I am currently seeing some latency with the application when running it against 2025. I am using the same version of my application, restoring the same back (creating from 2019 instance) and I am seeing additional latency on the newer instance.

I have ran the profiler against two of the areas I notice it the most and I am seeing where 2019, the application takes about 1.5 seconds but the 2025 tanks about 6 seconds. Once thing I am seeing is that when checking the details of the profiler the DB Time is about the same on both but the Own Time is what seems to be much larger.

I found a previous article showing how to use context for the profiler, the only problem is that the large time is on the business process as a whole and not within an onStart, onEnd, ect. so I am not really sure where to place that using statement. I have attached a screenshot of the profiler showing the BP taking 5,994 ms along with the stats of said BP showing DB Time is only 353 ms and Own Time is 4,823 ms.

This same BP when using a SQL 2019 instance tanks about 1,712 ms (much faster).

If anyone has any suggestions for possible ways to track down what might be causing the latency I would greatly appreciate it.

[Noam Honig]

I think that the difference you're seeing is a distraction - the own time there is the time of the UIController waiting for user input - so it's probably not that.

If you see a difference between sql server versions you should see it in the "red" lines - the ones that represent the db

Noam Honig  

Founder & CEO

www.fireflymigration.com

--
You received this message because you are subscribed to the Google Groups "Migrated By Firefly" group.
To unsubscribe from this group and stop receiving emails from it, send an email to migrated-by-fir...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/migrated-by-firefly/78053765-e9db-481e-b720-4b5a817f439bn%40googlegroups.com.

[Curt Malicoat]

Noam,

Thank you. Would there be any reason that UI waiting for user input would be affected by the database difference? The only difference is the database instance. Same application version, same server, same data just one lives in Sql 2019 and the other in Sql 2025. Also when this TankMaster UI controller runs there is no initial user input unless you consider passing parameters into the UI controller input. Is there any way to debug the OwnTime a little more to try an figure out why that increased in how long it takes?

Thanks,

Curt

[Noam Honig]

The ui wait is the time it took the user to end the profiler - that's why I treat it as noise.

Of this is a business process - than scratch my comment.

any sql time would be the red time - so I would try to follow that.


If you want to dive deeper into the own time - you'll need to use tools like jetprain profiler etc... that show you method by method

Noam Honig  

Founder & CEO

www.fireflymigration.com

To view this discussion visit https://groups.google.com/d/msgid/migrated-by-firefly/ec722126-1af5-45a0-9471-c82c4e99d8fen%40googlegroups.com.

[Curt Malicoat]

Ok, thanks Noam. I will try to see what I can figure out. The latency occurs prior to the UI even showing up on screen. I click the button and the increase in time is how long it takes the UI to show up after clicking the button. I am ending the profiler as soon as the UI shows up in both cases.

Thanks

[Harry Kleinsmit]

Hi Curt,

To avoid the UI you could also add the profiler into your code and run it just for the part where you think the bottleneck is.

See also: https://doc.fireflymigration.com/using-profiler-snippet.html

Best regards,

Harry Kleinsmit

Op dinsdag 9 juni 2026 om 16:12:56 UTC+2 schreef Curt Malicoat: