RE: Pride in Azure SQL Database

SSC Guru

Points: 1003863

May 9, 2018 at 6:47 pm

#1989973

Steve Jones - SSC Editor - Wednesday, May 9, 2018 5:06 PM
I'm still unsure of your complaint. If they hadn't done something that allowed you to workaround a change, you'd be upset? It sounds like you want to complain about the change, even though they anticipated potential issues and included the trace flag.
As for SP1, that's a problem for sure. I think it's embarrassing and unfair for them to issue patches with fundamental problems. Clearly there should be major RCA analysis on how/why that happens with a goal of reducing the chances of that in the future. I commend them for reacting and responding quickly, which is more than some vendors do.

No... I'm tickled that they have the trace flag to avoid using the "improved" cardinality estimator. Thank goodness they did.

Just like the point about SP1, though, you don't really have a choice as to when a change will be installed. Here it comes, ready or not. Thanks to their EULA, poor you if it kills something of yours. There's no recourse for shoddy workmanship in software, especially with MS, even if it's forced upon you.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)