Its here! The session details for our SQL-GLA event on 10th November 2017.
Running order & timing will be confirmed closer to the event & there will be 2 hours for networking & further discussions with speakers following the core sessions described below.
Introducing dbatools 1.0
After three years in beta, dbatools has finally reached 1.0! Whether you are a SQL Server DBA or developer, you’ll love what the SQL Server Community’s PowerShell module has to offer. Join us as we demo a ton of our favourite new commands that help make your life easier and your job more fun.
Query Store without SQL 2016 = Open Query Store
When SQL Server 2016 was released, it offered a fantastic new feature with the Query Store. Long term, statistics based, query tuning became a reality. But what about the thousands of servers that aren’t upgrading to SQL 2016 or newer? The open source project Open Query Store is designed to fulfil that need.
This session will give a short introduction to the Query Store feature in SQL 2016 and then dive into the Open Query Store (OQS) solution. William (on of the co-creators of the OQS project) will explain the design of OQS and demonstrate the features. You will leave this session with an understanding of the features of Query Store and Open Query Store, and a desire to implement OQS in your systems when you return to the office.
No More SQL Agent – Azure Automation for DBAs
The SQL Server agent was always the place where us DBAs would schedule everything we need to run unattended. In the cloud however, there are many tasks that need to run across the platform and not just on one virtual machine. And if you are using Azure SQL Databases, you don’t even have the Agent available.
PowerShell is the language of choice to automate but where and how do you host the scripts, and how do you schedule execution of these scripts?
This session is an introduction into Azure Automation using Runbooks and Azure DSC specifically aimed at DBAs. All demos will be based on typical tasks a “Cloud DBA” will need to perform.
Green is good; Red is bad – Turning your Checklists into Pester Tests
This session is for DBAs specifically, but will be relevant to any technicians who use checklists
I was required to prove that I had successfully installed and configured a backup solution across a large estate. I had a number of success criteria that had to be met. Checking all of these by hand (eye) would have been error prone, so I wrote a test to do this for me and an easy for management to read HTML report using PowerShell and Pester.
The session has come from that situation and is about enabling you to provide an easy to read output to quickly and repeatedly show that infrastructure is as expected for a set of checks, also known as Operational Validation using Pester. There are many use cases for this type of solution; DR testing, installation, first line checks, presentation setups
What is Pester?
Pester is a Unit Testing framework for PowerShell which can be used for testing your code but also as shown in this session for validating your infrastructure. There is an excellent post by Adam Bertram to introduce Pester. It is included with PowerShell on modern Operating Systems and free to download from the PowerShell Gallery or GitHub if not included.
After this session, you will have a basic understanding of how Pester works and the capability to examine your checklists and create your own validation tests and provide some reporting for management.
I am able to perform the following checks in 15 minutes across hundreds of servers and thousands of databases and I think it is cool and useful and everyone should be able to do so and take the functionality to create their own.
Every Job in Ola Hallengren’s Maintenance Solution exists, is enabled, has a schedule, has succeeded, has 2 job steps, has a generate restore script job step, the root backup folder is contactable, for every database the correct folders exist for the full, differential and log backup depending on recovery model in that folder, that each of those backup folders has files in it, that the most recent file in each of those folders is less than the required frequency for those jobs
Think about how long that would have taken a junior DBA if I had tasked them with it, and how many mistakes would have been made in the checking
A big thank you to our Sponsors for making this event possible!