It is second to human nature to compare when given options. When I wrote about the blog, SQL SERVER – Playing with Backups and Compression, I did compare some of the space savings one will achieve when working with backups and compression. Though the space savings were significant, one of the blog readers wanted to understand how this would be on time? Is it faster or slower to do the same. I went about taking the same script and I collected the time taken. Let us learn about Performance Analysis of Backup to Azure.
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 – Performance Choice – Coding or Automation
We talk a lot about optimizing SQL with building the most efficient queries and application architectures. It’s what we enjoy doing and what we’re paid to do. We love to twiddle bits and tweak code, and can spend day after day doing this. But are we looking at the big picture? Is what we are working on the highest priority for the business or organization we work for? Are we extending our value beyond just implementing and optimizing SQL databases and applications? Can we deliver value that has a return on investment (ROI) to organizations? That ROI can be in terms of making people more productive, saving infrastructure costs, and even making trade-offs for when we should code and when we should automate. This even applies to when to use consultants like me. Can an hour of consultation with me save days or weeks of research and trial-and-error in addressing a major performance roadblock?
SQL SERVER – Set AUTO_CLOSE Database Option to OFF for Better Performance
As many of you know, I am an indecent SQL Server Consultant, who purely focus on SQL Server Performance. Every single day, I keep two slots each hour long available for users who need my help urgently. I never ever pre-book them because, I believe it is critical to help people who needs help NOW. Well let us learn in this blog post about how I recently helped a customer to improve performance by turning off AUTO_CLOSE Database Option.
SQL SERVER – How to Hide Number of Rows Affected Message? – SET NOCOUNT
In this blog post, we are going to talk about how to hide the number of rows affected messages with the help of SET NOCOUNT.
SQL SERVER – 2016 – Wait Stats and Queues Script Updated – Identify Resource Bottlenecks
NOTE: This script will just work fine with earlier version of SQL Server (2008, 2012, 2014) along with SQL Server 2016. It will give the expected results in all the SQL Server versions. This script will help you identify resource bottlenecks in your SQL Server.
A few years ago, I wrote the script which will help us identify SQL Wait Stats and Queues. It is a very popular script. You can find the link to the script over here: Introduction to Wait Stats and Wait Types. However, it has been a long time since I wrote that script and it was written for SQL Server 2008.
SQL SERVER – Columnstore Index Cannot be Created When Computed Columns Exist
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.