Reputation
5,607
Top tag
Next privilege 10,000 Rep.
Access moderator tools
Badges
2 20 53
Impact
~685k people reached

Apr
28
comment Deadlock in SQL SERVER 2014
Have you tried using Adam Machanic's sp_whoisactive to see what's going on while you're dropping? This will tell you who's really holding onto the table you're trying to drop. Use @find_block_leaders=1 and @sort_order='[blocked_session_count]DESC' to make the output easier to visualize
Apr
26
comment Cardinality Estimator Question after 2014 SP1 + CU4 Upgrade
Hi @Shanky , I am going to take a step back from this problem for now. So far, unless the cardinality estimator is in v70, the execution times are too long. I'm going with your other suggestion to use querytraceon with the queries that suffered most from v120. Still if the statistics are updated using v70 and not v120, how can I be sure the execution plans created for my tests are accurate?
Apr
26
comment Cardinality Estimator Question after 2014 SP1 + CU4 Upgrade
Thanks Chris, I too had read that article but thought that the 4199 traceflag would implement the new estimator.
Apr
26
revised Cardinality Estimator Question after 2014 SP1 + CU4 Upgrade
added 414 characters in body
Apr
25
comment Cardinality Estimator Question after 2014 SP1 + CU4 Upgrade
So I'm back to square one after switching over to 4199 and updating statistics again. Execution times were up and the CPU was once again maxing out. A deeper analysis of what's going on will be necessary. One of my coworkers jokingly said that we'll probably end up using the 2014 cardinality estimator with the 2016 version of MSSQL.
Apr
25
comment Cardinality Estimator Question after 2014 SP1 + CU4 Upgrade
hello Shanky and thanks for the assist. So if I understand you correctly, there may be corrections to the cardinality estimator but they won't be effective unless I enable traceflag 4199?
Apr
25
comment Cardinality Estimator Question after 2014 SP1 + CU4 Upgrade
Hello Cody, the statistics are being updated using a FULLSCAN. Considering the thousands of complex queries involved, it won't be possible to analyze all of their execution plans one by one
Apr
25
asked Cardinality Estimator Question after 2014 SP1 + CU4 Upgrade
Mar
21
awarded  Popular Question
Feb
25
awarded  sql-server
Feb
16
awarded  Popular Question
Jan
19
awarded  Popular Question
Jan
11
accepted RESTORE FROM URL dies during database recovery
Jan
11
revised RESTORE FROM URL dies during database recovery
deleted 441 characters in body
Jan
8
revised RESTORE FROM URL dies during database recovery
added 527 characters in body
Jan
8
revised RESTORE FROM URL dies during database recovery
added 135 characters in body
Jan
8
comment RESTORE FROM URL dies during database recovery
Hi @AaronBertrand, I updated my question and added an answer. I opened up a case with Microsoft, perhaps they will find a way to make the restore from URL work with so many vlfs to restore.
Jan
8
answered RESTORE FROM URL dies during database recovery
Jan
8
revised RESTORE FROM URL dies during database recovery
added 4218 characters in body
Jan
5
revised RESTORE FROM URL dies during database recovery
added 135 characters in body