In 2025.3 some smoke tests for a unique primary key on a view could be very slow (timeout). When I leave out the TOP 1 in the statement it performs much better.
Is this a known issue?
Question
Smoke test (primary key unique) performance
Hi Andre,
I think it would be good to create a ticket for this so we can investigate it further. There may be some optimization opportunities in this smoke test.
Some additional details about the view would be helpful as well, such as the amount of data it contains and, if possible, the execution plans for both variants.
Regards,
Dick van den Brink
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.