Welcome to self-paced labs to learn SQL Server on Linux and Docker Containers.
To use these self-paced labs you must go through installation of Linux and tools by going through the prelab. Follow the instruction in the readme.md in the prelab folder.
The self-paced labs should be done in the following order. Note the lab on containers and appcompat can be done separately after the prelab. The labs on deploy_and_explore and auto_tune need to be done together and in order.
-
The prelab involves installing an Azure Virtual Machine with Red Hat Enterprise Linux and tools for your laptop to complete the rest of the labs.
-
In this lab you will learn how to deploy SQL Server, explore files from the SQL Installation, explore various common Linux commands and the bash shell, and perform basic tests to connect to SQL Server on Linux.
-
In this lab you will learn how to observe the Automatic Tuning Feature of SQL Server using SQL Operations Studio. You will learn basics of how to use SQL Operations Studio while understanding how Automatic Tuning can help customers resolve query plan regression problems.
-
In this lab you will learn the basics of SQL Server with docker containers. Then you will apply these skills to deploy an ASP.Net application using containers. This application uses SQL Server engine features that apply across both SQL Server on Windows and Linux.
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.