January 17, 2021 at 4:03 pm
From our software provided by a third party vendor, I am seeing the following:
They use prepared statements with Microsoft JDBC Driver for SQL Server
The same statement will get executed 20-30 times over a 5 minute span - it will get executed with:
sp_execute
sp_executesql
sp_prepexec
Execution times are erratic....sometimes decent...sometime horrific.....hit or miss.
The statement is rather complex and should be broken down into steps with a SP, but they will not change
What will cause the 3 different methods of execution listed above?
Outside of changing the code (I have no access), what others measures can be taken?
How can I prove to them that something is wrong with their code / design?
Thank you in advance.
January 18, 2021 at 4:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
January 21, 2021 at 3:09 pm
Does anybody have anything on this scenario?
January 25, 2021 at 1:13 pm
one last try....anyone?
January 25, 2021 at 1:48 pm
There's some info here: https://www.sqlservercentral.com/forums/topic/sp_prepexec-vs-stored-procedures
...and here: https://www.brentozar.com/archive/2018/03/sp_prepare-isnt-good-sp_executesql-performance/
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply