Transaction Search is running slowly on SQL Server 2016 compatibility level 130 or higher.

When running SQL Server 2016 compatibility level 130 or higher, users have noticed that running a "Transaction Search" takes around 20 seconds to find a single transaction when doing a search using the "Revenue ID" in the search form. 

Doing the same search using compatibility level 110 (SQL 2012 DB level) returns a result almost instantly. 
We’re currently evaluating this issue for a fix in a future release.

Environment

 Blackbaud CRM
 4.0
 4.0.180.1600

Was this article helpful?


Thanks for your feedback! Did this solve your issue?

Comments (optional):


Thanks for your feedback!
We're glad it was helpful but sorry it didn’t solve your issue. If you need assistance, click Chat with Support below.
We’re sorry to hear that. Please tell us why.

 I don't like how this works.

 The answer is confusing.

 The answer didn't match what I was searching for.

Additional Comments (optional):


Thanks for your feedback! If you need assistance, click Chat with Support below.
Thanks for your feedback. Help us make our products even better by sharing details in our Idea Banks or our online Community.
Thanks for letting us know. We'll work on clarifying the information in the article. If you need assistance, click Chat with Support below.
Thanks for letting us know. We'll work on updating the search engine to return more relevant results.