fix performance #3539

[sleupold]

thanks to @eugene-sea for bringing up and testing this issue.

[mitchelsellers]

With some local testing on a large DB this seems to preform well.

[david-poindexter]

@sleupold what issue does this PR address?

@mitchelsellers are we trying to get this in 9.5.0 or 9.5.1?

[valadas]

Looks good to me

[sleupold]

@david-poindexter

@sleupold what issue does this PR address?

stated in the title: #3539

@valadas this PR supersedes #3474 , which may be closed now.

[valadas]

@sleupold

stated in the title: #3539

I would be nice next time to have a human readable title only and to put something like:
Closes #3539 or Fixes #3539 in the description.
This would make it easier for release notes and it will close the issue automatically when merged which does not happen when done in the title.

[sleupold]

thanks for the instructions, @valadas

[dimarobert]

@sleupold @mitchelsellers found this while upgrading some of our internal sites.

[dimarobert]

databaseOwner and objectQualifier were needed here. Because of this, the Scheduler in 9.5.0 fails to execute this stored procedure.

[dimarobert]

here as well.

[valadas]

Thanks for spotting that @dimarobert , however this was already merged. Could you create a new issues about this to make it more actionable please, and well if you can submit a PR that fixes it, even better :)

[sleupold]

I'll create a PR for DNN 9.5.1

[dimarobert]

@sleupold I've created an issue and PR here: #3604

[sleupold]

@dimarobert
your fix is perfect to apply as a workaround for anyone. running DNN 9.5.0 (using non-default object qualifier and/or schema name), but to fix it for future DNN versions, it needs to be adjusted.