From the course: SQL Server Containerization: Modern Deployment Strategies for Data-Driven Organizations

Unlock this course with a free trial

Join today to access over 25,500 courses taught by industry experts.

Deploying and accessing SQL Server using Docker

Deploying and accessing SQL Server using Docker

- [Instructor] Deploying a SQL Server on containers is very similar to self-managed deployment on Linux. You start by picking a version of SQL Server, however this time, it comes from a container registry, which is also nothing else than a web-based repository. The container registry will again offer you all the available versions and CUs of SQL Server with the latest CU of each SQL Server major release being tagged as Latest. In theory, for example, in disconnected scenarios, you can also run your own container registry and cache the Microsoft images there, but we'll stick to using the public registry. An optional step will be to pre-pull or download the required containers. When running a container, the first thing the container runtime will do is check if the image already exists or not, and if not, it'll download it. But what if you have connectivity issues at some point? By pre-pulling, you're simply ensure that the container's already present. The last step is then to simply run…

Contents