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

Querying and data manipulation


Now that we have a memory-optimized table, the next logical step is to start querying the table and manipulating the data stored inside it.

We have two methods of interacting with these memory-optimized objects. Firstly, we can issue standard T-SQL queries and allow the SQL Server Query Optimizer to deal with accessing this new type of table. The second method is to use Natively Compiled Stored Procedures.

Figure 11.4: Overview of the SQL Server engine illustrating Query Interop between In-Memory OLTP and "normal" OLTP

In Figure 11.4, we can see a simplified diagram of a query that is either querying "normal" tables or memory-optimized tables. In the center of the diagram is a node titled Query Interop. This is a mechanism that is responsible for enabling "normal" interpreted T-SQL statements to access memory optimized tables. Note that this is a one-way mechanism and that the natively compiled stored procedures are not able to access traditional objects, only...

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