Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
SQL Server 2016 Developer's Guide

You're reading from  SQL Server 2016 Developer's Guide

Product type Book
Published in Mar 2017
Publisher Packt
ISBN-13 9781786465344
Pages 616 pages
Edition 1st Edition
Languages
Authors (3):
Miloš Radivojević Miloš Radivojević
Profile icon Miloš Radivojević
Dejan Sarka Dejan Sarka
Profile icon Dejan Sarka
William Durkin William Durkin
Profile icon William Durkin
View More author details
Toc

Table of Contents (21) Chapters close

SQL Server 2016 Developer's Guide
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
1. Introduction to SQL Server 2016 2. Review of SQL Server Features for Developers 3. SQL Server Tools 4. Transact-SQL Enhancements 5. JSON Support in SQL Server 6. Stretch Database 7. Temporal Tables 8. Tightening the Security 9. Query Store 10. Columnstore Indexes 11. Introducing SQL Server In-Memory OLTP 12. In-Memory OLTP Improvements in SQL Server 2016 13. Supporting R in SQL Server 14. Data Exploration and Predictive Modeling with R in SQL Server

What is missing in SQL Server 2016?


SQL Server 2016 is the first SQL Server version that has some built-in support for temporal data. However, the support is still quite basic. SQL Server 2016 supports system-versioned tables only. You saw at the beginning of this chapter that application-versioned tables, and of course bitemporal tables, add much more to the complexity of temporal problems. Unfortunately, in order to deal with application validity times, you need to develop your own solution, including your own implementation of all the constraints you need to enforce data integrity. In addition, you need to deal with the optimization of temporal queries by yourself as well.

It would also be nice if you were able to define the retention period for the historical rows, like you can define for the Query Store. Currently, you have to do the history data cleanup by yourself.

If you are familiar with analytical applications and data warehouses, you might think that system-versioned temporal tables...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at ₹800/month. Cancel anytime