Explorations working with SQL Server never stop and I get an opportunity to learn something every other day. Today I thought of bringing pout some learning that happened to me by accident. As I was not sure and assumed certain things, these came as a surprise learning for me. So let us see what is the issue at hand, which is about Columnstore Index and Computed Column.
SQL SERVER – Identifying If Database Supports InMemory OLTP Functionality
I had recently received an email about InMemory OLTP Functionality in Email when I was having a vacation with my family in the Australia.
SQL SERVER 2016 – InMemory OLTP LOB Datatype Enhancement
My exploration with SQL Server 2016 features are just continuing and I am delighted every other day to figure out something new been added to the capabilities which in the opinion were of limited capacity in the prior versions of SQL Server. I will spare the ranting exercise for now but will look at some of the things that caught my attention in my recent exploration with SQL Server InMemory OLTP enhancements.
SQL SERVER – Identifying InMemory OLTP Hash Collisions
It is about a few weeks back that I wrote about how InMemory OLTP Hash Collisions can happen and how it can affect performance. Here is a recap of that post for your reference and do check the same before proceeding reading this blog post.
SQL SERVER – Finding Waits For Any Session with Extended Event wait_info
It becomes a great win-win situation. Let us learn about Extended Event wait_info in this blog post. Do you think this script will be useful for you?
SQL Server – InMemory OLTP Hash Collisions Performance Overhead
Sometimes the best of learnings are based on people’s questions. I always feel when questions are asked, more the learnings are. In a recent session for a customer who had implemented SQL Server 2014 InMemory OLTP in their systems, they were getting bad performance even when they were using InMemory OLTP.






