MyPage is a personalized page based on your interests.The page is customized to help you to find content that matters you the most.

I'm not curious

An Introduction to Docker and Containers for SQL Server Developers and DBAs

Published on 15 September 17
In March 2013 Soloman Hykes announced what would become known as the Docker open source project. In the months that followed there was a ground swell of adoption by the Linux community, and in the fall of 2014 Microsoft announced plans to implement containers in Windows Server 2016. WinDocks, where I am a co-founder, released an independent port of Docker’s open source to Windows in early 2016, with a focus on first-class container support to SQL Server.

Containers are rapidly become a strategic focus across the industry. In this article we’ll look at containers and their use by SQL Server DBAs and developers.

Understanding Containers

Containers define a new method of application packaging combined with user and process isolation, for application multi-tenancy. Varied Linux and Windows container implementations have existed for years, but Microsoft’s release of Windows Server 2016 established Docker’s design as the defacto container standard. The Docker API and container format is now supported on AWS, Azure, Google Cloud, every Linux distro, and Windows. Docker’s design is elegant and delivers compelling benefits:

Portability: containers include application software dependencies and run unmodified on a developer’s laptop, a shared test server, or any public cloud.

Container ecosystem: the Docker API is the focus for industry-wide innovation, with monitoring, logging, storae, security, cluster orchestration and management solutions.
Cloud native: containers are designed for micro service architectures, for horizontal scale out, and for ephemeral workloads. Containers are designed to be discarded and replaced, not patched or upgraded.
Speed and economy: containers are created in seconds, with efficient application multi-tenant support. Most users realize a 3-5x reduction in VMs used.
Why SQL Server Containers?
SQL Server has supported multitenancy with named instances for the past decade, so how are SQL Server containers valuable?
The answer is that SQL Server containers are more practical by their speed and automation. SQL Server containers are named instances, complete with data and configuration, delivered in seconds. The ability to create, discard, and replace SQL Server containers in seconds creates more practical use for Dev and QA, and other uses as we’ll discuss below.
The speed and automation of SQL Server containers make them ideal for delivery of production data environments for Dev and QA. Each member of a team works with isolated containers on a shared VM, with a 3-5x reduction in VMs used. This translates to significant savings on VM maintenance, and Microsoft license cost savings. Containers are also easily integrated with Storage Area Network (SAN) arrays, using storage replicas and database clones.

Read more
This blog is listed under Open Source and Data & Information Management Community

Related Posts:
Post a Comment

Please notify me the replies via email.

  • We hope the conversations that take place on will be constructive and thought-provoking.
  • To ensure the quality of the discussion, our moderators may review/edit the comments for clarity and relevance.
  • Comments that are promotional, mean-spirited, or off-topic may be deleted per the moderators' judgment.
You may also be interested in
Awards & Accolades for MyTechLogy
Winner of
Top 100 Asia
Finalist at SiTF Awards 2014 under the category Best Social & Community Product
Finalist at HR Vendor of the Year 2015 Awards under the category Best Learning Management System
Finalist at HR Vendor of the Year 2015 Awards under the category Best Talent Management Software
Hidden Image Url