Today’s blog post created from a recent conversation with one of my customers. They asked me a very interesting question – “When should they hire me for my famous Comprehensive Database Performance Health Check?”. I send them following 10 questions and told them to take a quick quiz about their SQL Server Environment. They replied back to with YES to all the answers. If the answer to any of the following questions in YES, that means user can for sure improve your SQL Server’s Performance. After taking this quick test, my customer realized that they have amazing potential to improve the performance of their server.
In the month of January, I offered exclusive training to my newsletter subscribers. The training was extremely unique and was available for a limited time. Quite a lot of newsletter subscribers took advantage of this limited time offer of “SQL Server Performance Tuning Practical Workshop”.
Question: How do I find out how many queries have an Implicit Conversion in SQL Server? The source of this question is very interesting.
Earlier this year, I was fortunate to take part in the first edition of the Group By Conference organized by Brent Ozar. I was extremely fortunate that I was able to present an hour long presentation on the subject 3 Common Mistakes to Kill SQL Server Performance.
I guess, it is no secret that testing plays a critical part in development of any software product. The more rigorous testing is, the better the final product will be. In this blog post we will be Testing Database Performance with tSQLt and SQLQueryStress.
In this blog post we are going to leave about how to Speed Up Performance Without Code Change or Configuration Change in SQL Server.
There is always more than one way to do one thing in any programming languages. In SQL Server there is always more than one way to achieve same result set. It is quite often I see that developers write subqueries in place of joins or joins in place subqueries.