Timeline for Performance issues after moving a database to SQL Server 2014
Current License: CC BY-SA 3.0
32 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 11, 2018 at 3:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jul 31, 2018 at 20:01 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jun 30, 2018 at 19:40 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| May 27, 2018 at 7:22 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Apr 26, 2018 at 12:22 | comment | added | Jonathan Fite | Can't see where anyone has asked you to confirm similar/better hardware or server configuration. (CPU, Memory, Disks, Server Min/Max Memory, disk configuration (where are tempdb and the data/log files?), etc. MaxDOP, Cost Threshold for Parallelism, trace flags... | |
| Apr 26, 2018 at 11:48 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Mar 20, 2018 at 23:30 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Feb 18, 2018 at 10:07 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jan 16, 2018 at 19:38 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Dec 12, 2017 at 14:38 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Nov 11, 2017 at 13:21 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Oct 10, 2017 at 21:50 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Sep 8, 2017 at 2:11 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Aug 4, 2017 at 23:36 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jul 5, 2017 at 10:39 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jun 5, 2017 at 7:05 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Feb 3, 2017 at 4:44 | comment | added | Joe Obbish | For the "slow" query, can you confirm that's the one running with 120 compatibility level that took 12 hours to finish? I took a look at it and couldn't find anything that would make it take 12 hours to run. Maybe I missed something. | |
| Feb 2, 2017 at 21:39 | history | edited | Sam | CC BY-SA 3.0 |
deleted 10582 characters in body
|
| Feb 1, 2017 at 10:16 | answer | added | T.H. | timeline score: 2 | |
| Jan 30, 2017 at 17:16 | answer | added | T.H. | timeline score: 1 | |
| Jan 30, 2017 at 14:16 | comment | added | Sam | I've added links to the execution plans in the post. | |
| Jan 30, 2017 at 13:45 | history | edited | Sam | CC BY-SA 3.0 |
Edited to add execution plans
|
| Jan 28, 2017 at 0:37 | comment | added | Joe Obbish | Please add execution plans for the poorly performing query to your question. It would be helpful to upload one as is and one with RECOMPILE and QUERYTRACEON 9481 hints. That will let us rule out the new CE as being a problem. Try brentozar.com/pastetheplan for uploading the plans. | |
| Jan 27, 2017 at 22:56 | comment | added | RLF |
I assume that you used RESTORE. But, out of curiosity, did you detach the files from the other server, copy it to the new server, and then attach the database files.
|
|
| Jan 27, 2017 at 16:08 | comment | added | Sam | Not entirely sure how to upload an execution plan here, but I can tell you that the choke points seem to be on the Index Seek and Key Look ups for the | |
| Jan 27, 2017 at 16:07 | history | edited | Sam | CC BY-SA 3.0 |
added 10588 characters in body
|
| Jan 27, 2017 at 15:32 | comment | added | David דודו Markovitz | Hi Sam, can you share one of the queries including execution plan? thanks | |
| Jan 27, 2017 at 14:44 | comment | added | Scott Hodgin - Retired | This is most likely caused by the new cardinality estimator in Sql 2014 - msdn.microsoft.com/en-us/library/dn600374(v=sql.120).aspx | |
| S Jan 27, 2017 at 14:42 | history | suggested | Ian_H |
Version tags added
|
|
| Jan 27, 2017 at 14:41 | review | Suggested edits | |||
| S Jan 27, 2017 at 14:42 | |||||
| Jan 27, 2017 at 14:38 | review | First posts | |||
| Jan 27, 2017 at 14:57 | |||||
| Jan 27, 2017 at 14:37 | history | asked | Sam | CC BY-SA 3.0 |