SQL Server 2016 brought several innovations. One of the most anticipated feature additions was the ability to define foreign keys with InMemory tables. I wrote about this feature earlier on blog at: SQL SERVER 2016 – InMemory OLTP support for Foreign Key.
SQL SERVER – Using dm_db_stats_properties With InMemory OLTP Tables
The whole concept of InMemory OLTP has been around for a while and still there are areas that I try to go back to learn every single time. If you are new to InMemory OLTP, I would highly recommend searching this blog for more content. For a starter, the blow blog is a great start.
SQL SERVER – How to Find the In-Memory OLTP Tables Memory Usage on the Server
When I presented at the SQLPASS this year there were several learning that I found it interesting. Every year, this presentation preparation is something I take it seriously. I know many them turn up to learn some new tricks every single year. Hence, I invest considerable amount of time to prepare. This year I showcased several tips and tricks involving SQL Server In-Memory OLTP capability. I personally feel this feature is lesser known and never appreciated. As I was doing the session, one of the DBA asked how to find out the memory utilization of various In-Memory OLTP tables.
SQL SERVER – Fix Error Msg 10794, Level 16 – The operation ‘CREATE INDEX’ is not supported with memory optimized tables.
Whenever I write something as a new concept, I do see people reading the blog do give it a try. Many a times I get queries that the script didn’t work for them after they learnt the concepts about memory optimized tables. The blog I wrote on how In Memory OLTP was supporting ColumnStore – read it: SQL SERVER – Creating Clustered ColumnStore with InMemory OLTP Tables
SQL SERVER – Creating Clustered ColumnStore with InMemory OLTP Tables
When SQL Server 2016 was released, there were a number of enhancements that were discussed around how InMemory OLTP removed which were as limitations. I personally saw some real boot to some of the capabilities coming into InMemory OLTP especially around the concept called as Operational Analytics that Microsoft calls in this release. I am going to talk about this concept in my SQLPass session later this month in October but here is a teaser for what I learnt from this concept.
SQL SERVER 2016 – Creating Clustered ColumnStore with InMemory OLTP Tables
I have been writing a lot of my findings with SQL Server 2016 in the recent past. This is also being something I have been investing big time keeping my session at SQLPASS coming in the October timeframe. I will be talking on a number of capabilities and enhancements around SQL Server 2016 from a performance standpoint that it is critical for me to explore some. I invest considerable time in preparation for any session and every single year going to SQLPASS has been the highlight and most of the time it is about hard work to make sure everyone attending my session gets the best of content. Also, it is a great way for me to do due diligence and homework as I prepare with real world problem statement with possible alternatives and solutions as part of my session. Let us learn about Creating Clustered ColumnStore with InMemory OLTP Tables.
SQL SERVER – Fix Error Msg 35336 Working with ColumnStore Indexes
Since my consulting have started around performance tuning, I am able to see a number of customers who want to start using the new capabilities of SQL Server for their existing application as they plan to do an upgrade of their infrastructure. In one of engagement with a bank, who was upgrading their SQL Server 2012 to SQL Server 2016, they were interested in knowing how some of the new InMemory or even usage of ColumnStore Indexes can be used. It was an interesting conversation that started which I am using as a blog here.