Not just the query store, but the whole SQL 2016 is a SNAFU

The same single select query with no joins and only two fields in its where clause completed in 10-20 seconds before the upgrade from SQL 2012, and now it completes in 1 min 40 seconds. Nothing changed, but the SQL server version. Even with hundreds of billions $$ Microsoft FUBARs everything they change as of lately.

Posted by: LinuxLies at 11:37 AM | No Comments | Add Comment
Post contains 82 words, total size 1 kb.

Query store in MS SQL Server 2016 is totally messed up

A wonderful new tool, allowing us to see what is going on in real time by storing query plans and basic stats, is a complete SNAFU.

Information of plan execution count is completely misleading, as it can jump up and down as the queries execute. WTF, Microsoft? How come a query, which according to you just executed 7000 times, all of a sudden has 9500 executions, but oh, wait, it's back to 7005... And up to 9700 again. Make up your mind, will you?

It's getting worse if we time query execution using other methods, such as diagnostic logging or running SQL Profile. The figures gathered by the query store, especially last execution time, are completely out of whack and out of touch with reality.

With all your hundreds of billions, how can you, Microsoft, F up everything so badly, all the time, every time?

Posted by: LinuxLies at 05:14 PM | No Comments | Add Comment
Post contains 167 words, total size 1 kb.