We have been able to spin up an instance of SQL Server inside a container. We have seen that a rapid deployment is possible once the image and supporting files are available on the container host system. The general idea behind containers is that they can be quickly created and destroyed at will, allowing for rapid deployments and short-lived instances of applications (great for testing/development). Once we have these files available, creating and destroying an instance of SQL Server is almost instantaneous and we can begin treating our database service just like a simple web server—a stateless relational database processing service. However, just because the database engine now enjoys rapid deployment, we must ...
Data persistence with Docker
Get SQL Server 2017 Developer's Guide now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
