Andreas Wolter • 8/9/2017

Optimizing workflows with In-Memory and Natively Compiled Objects – or how it does not work

Read Original

This technical article analyzes a common ETL workflow optimization attempt using SQL Server's In-Memory features (memory-optimized tables, TVPs, natively compiled procedures). It details a scenario where replacing a temporary table with a memory-optimized table-valued parameter unexpectedly leads to similar or worse performance due to persistent disk I/O and locking in interop mode, concluding there is no 'quick win'.

0 comments
#SQL Server #Table Valued Parameters #Xtp Engine
Optimizing workflows with In-Memory and Natively Compiled Objects – or how it does not work

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
Quoting Thariq Shihipar
Simon Willison • 2 votes
2
Top picks — 2026 January
Paweł Grzybek • 1 votes
3
In Praise of –dry-run
Henrik Warne • 1 votes
4
Deep Learning is Powerful Because It Makes Hard Things Easy - Reflections 10 Years On
Ferenc Huszár • 1 votes
5
Vibe coding your first iOS app
William Denniss • 1 votes
6
AGI, ASI, A*I – Do we have all we need to get there?
John D. Cook • 1 votes
7
Dew Drop – January 15, 2026 (#4583)
Alvin Ashcraft • 1 votes