Timeline for SQL Server 2016, temporal tables and compressed indexes
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 31, 2018 at 13:42 | comment | added | David Browne - Microsoft | Also since SQL 2016 SP1 was released more than 12 months ago, SQL 2016 RTM is now out of support. | |
| Jul 31, 2018 at 12:43 | comment | added | Aaron Bertrand | (I wonder if the abnormal psychology warning could be made less prominent if the user is on 2016 RTM and suppressed entirely on 2016 SP1+, especially in the case where it's only found on temporal tables?) | |
| Jul 31, 2018 at 12:41 | comment | added | Aaron Bertrand | Right, this is an FYI in this case because before SQL Server 2016 SP1, a compressed index couldn't be restored on Standard Edition. If you are in the small window between temporal tables introduced (2016 RTM) and compression opened to all editions (2016 SP1), you can't back up that database and restore it on a 2016 RTM Standard Edition, for example. This is easy to work around: upgrade the target to SP1 or higher (or remove history, re-create the indexes without compression, and re-enable history). For most other implementations, the warning serves a broader audience (e.g. everyone < 2016). | |
| Jul 31, 2018 at 12:39 | vote | accept | Lewis Veale | ||
| Jul 31, 2018 at 12:23 | history | edited | Erik Reasonable Rates Darling | CC BY-SA 4.0 |
added 85 characters in body
|
| Jul 31, 2018 at 11:59 | history | edited | Stijn Wynants | CC BY-SA 4.0 |
added 17 characters in body
|
| Jul 31, 2018 at 11:43 | history | answered | Stijn Wynants | CC BY-SA 4.0 |