(Michael Otey) Licensing of Microsoft products has always been complicated, and SQL Server 2016 is no exception. To make matters worse, it can be deployed in a number of different scenarios that can confuse licensing requirements even further.

(Kunal Chandratre) The Microsoft Azure Platform is huge. This article provide some quick access information and important links about all the services that are offered on Azure.

(Robert Sheldon) Distribution statistics are used by SQL Server’s Query Optimiser to determine a good execution plan for your SQL query. You don’t need to know about them to execute queries, but the better you understand them, the better you can optimise your queries and sort out performance problem

(Vadivel) In SQL Server Management Studio:

(Rajendra Gupta) In an earlier tip SQL Server 2016 Database Scoped Configuration, we provided an overview of the important parameters that can be set at the database level which were previously available at the instance level only. In this tip we are going to explore this functionality in more detai

(Pinal Dave) I had recently received an email about InMemory OLTP Functionality in Email when I was having a vacation with my family in the Australia. Let us read the story about my vacation and SQL Server in this blog post.

(Andrew Pruski) Ok, so this is old news I know, but I’ve had a busy couple of months and am only getting around to writing this now. SSMS is now a separate release from SQL itself. The latest release is here.

(Jason Brimhall) When working with Extended Events, there are times when a little more information is, well, helpful. You know you want to use extended events to try and monitor for a specific thing xvnt_crossingto happen.

(Prashanth Jayaram) Inventory is a vital information,whether you’re a consultant or an in-house DBA, you need to have a reliable inventory of the servers you manage.This inventory can take any number of forms but, ideally, will allow some aggregation of information.

(Pinal Dave) I have seen a number of customers manage their SQL Server environments in an adhoc manner. These accidental DBA’s need to know what happened in the system in a chronological order or even worst need to know what led to the lead up to a particular problem.