Why should I use Query Store? Query store can be used for a number of things. For example: Find out what was happening on my server last night? Identify and fix queries suffering from parameter sniffing or plan regression Testing (ie - when upgrading to a new version of SQL server, or development) What happened on my server last night? Query store is great for a historical view into what your server was doing. It's often referred to as "a flight data recorder". There were so

It's amazing that we never had a built in feature that logged historical record of queries. Sure we had the plan cache, but that was cleared with a service restart or reboot. How many times have you walked into an environment and they would say the server was slow yesterday, or at 2:00am last night, what happened? Well, it's tough to pin point if you didn't create some means of logging (hint: try logging the output of sp_whoisactive periodically!) or a third party tool. What

Before we begin: While the gui/wizard for setting up Availability groups is super easy, I'm going to go through utilizing T-SQL. This gives us an "Under the hood" look at the way these are setup. I will provide the full script at the end of the post. As an FYI, I will be using SQL 2017 Developer edition running on Windows Server 2016 in my virtual lab. (Running on Hyper-V). Installing SQL Server: The installation of SQL Server on each node is a basic Standalone installation.