SQL Server Containers and Clones

Target Audience:

SQL Server DBAs and Developers.


Microsoft emphasizes use of containers for development and test on SQL Server 2017, and new solutions from Red Gate and Windocks add support for containers and SQL Server database cloning  for the full range of the SQL Server family. We’ll explore use of containers for delivery of container environments, and their pros and cons. We’ll also look at SQL Server cloning, and how clones enable Dev and Test teams to work on large database environments for containers as well as existing SQL Server instances.

Containers and Clones are particularly well suited for Public and Hybrid Cloud, as it’s infrastructure agnostic. Container images are ultimately portable, and the built-in database cloning is especially useful on public clouds.

Audio podcast:

Enjoy the Podcast?

Don’t miss an episode, subscribe via iTunes, Stitcher or RSS
Leave us a review in iTunes

Why I want to present this session:

Provisioning SQL Server environments for testing is one of the challenges facing most organizations today. The advent of SQL Server containers combined with SQL Server database cloning offers dramatic improvements in speed and efficiency in automated provisioning of writable environments for Dev and Test purposes.

The following two tabs change content below.

Paul Stanton

Co-founder, VP at Windocks
Former Microsoft, co-founder of Windocks. I've been involved in Windows container solutions for Cloud Foundry, OpenShift, and Docker. I lead Windocks Product Management and Marketing, with Windocks becoming the first container engine to include database cloning, and am leading the firm to become the first open enterprise data delivery platform.

Latest posts by Paul Stanton (see all)

Previous Post
Be My Azure DBA (DSA)
Next Post
Architecting Availability Groups

1 Comment. Leave new

Howdy sir! Thanks for the abstract. Here’s my feedback thoughts:

First, the target audience is casting a really wide net, but I don’t think the abstract is really going to catch the fish. The abstract is very passive, very broad, and sounds like it’s going to be a 100-level marketing slide deck of screenshots. There are times where that works really well – but if you’re going to win an audience voting with that, you’ve gotta really go in guns blazing. As it is, the lack of comments kinda tells you something – it just doesn’t hook the audience.

Containers are definitely a hot topic, but maybe consider focusing on the pains they solve rather than describing the solution. Check this out: https://ozar.me/2015/02/best-presentations-based-pain/

Side note – I don’t think you need capitals for Dev, Test, Public, Hybrid, and Cloud. They’re not proper nouns.


Leave a Reply

Your email address will not be published. Required fields are marked *

Fill out this field
Fill out this field
Please enter a valid email address.