When Memory-Optimized Tables (MOT) were announced for SQL Server, there was a lot of excitement about the technology. After this was released on SQL Server 2014, feelings waned with a lot of restrictions and limitations for using the technology. I remember a panel at a conference years ago where most of the MVPs and experts recommended against using the technology for most users.
Today there have been improvements (2017, 2016) in the MOT features, restrictions have been removed, and all editions can use MOT tables. That’s not to say that this is suitable for every table or situation where a DBA or developer suspects performance issues.
This month I want to ask you about when you’ve made that decision. This can be to use MOT tables or NOT to use MOT tables. This could be a simple thought, a POC, or actual testing of the feature.
Some ideas for you to write about:
- Performance analysis of MOT tables that affected a decision
- Reading the limitations and knowing this would prevent their use
- A scenario where MOT tables improved performance
- A successful implementation of MOT tables and what needed to change in your app
- A failed attempt at trying MOT tables
There might be other things that are related to MOT technology, but let us know this month what you think of the technology and how it has (or has not) impacted your application.
The Rules
Here are the rules as set out for the T-SQL Tuesday blog party.
- Your post should be published on Tuesday, Aug 13, 2019 between midnight UTC and 11:59:59 UTC.
- Include the T-SQL Tuesday logo in your post.
- Link back to this invitation.
- Include a comment on the invitation post or a trackback link.
- Enjoy the chance to be creative and share some knowledge.
