CF Swarm: End-to-End Coldfusion Pipeline with Cont
  • Preface: Who Is This Guide For?
  • About the Author & License
  • Part 1: What Containers Mean To Web Applications (and You)
  • Part 2: Before You Begin
  • Part 3: Docker in Development
    • Installing Docker: Initial Setup
    • Running Docker: Clone a Working Development Stack
    • docker-compose.yml: A Closer Look
    • nginx.conf: Reverse Proxy to a CF Engine
  • Part 4: Building Images and Container Registries
    • Our First Image: A Sample Build Environment
  • Part 5: Choosing a Cloud Infrastructure Provider
  • Part 6: The Production Network Layout (How Many Instances and What Kind)
    • Your First Instance: Provisioning
    • Your First Instance: Basic Configuration & Security
    • Your First Instance: (Optional) Provider-Level Firewall
    • Your First Instance: Taking A Snapshot
  • Part 7: Production Setup (Outside the Swarm)
    • Pipeline Setup: Instance Prep
    • Pipeline Setup: VPN Server
    • Pipeline Setup: Source Control & Container Registry
    • Pipeline Setup: Database Prep
      • Pipeline Setup: MySQL
    • Pipeline Setup: Microsoft SQL Server
    • Pipeline Setup: Provider Firewall
  • Part 8: Production Setup (The Swarm)
    • Container Strategy
  • Credits & Acknowledgments
Powered by GitBook
On this page
  • Moving the Default Data, Log, and Master DB Directories
  • Allow Ports 1433 and 1434 through your OS Firewall
  1. Part 7: Production Setup (Outside the Swarm)

Pipeline Setup: Microsoft SQL Server

PreviousPipeline Setup: MySQLNextPipeline Setup: Provider Firewall

Last updated 6 years ago

Time Required: 10-15 Minutes (Setup: 5-10 Minutes; Data Relocation: 5 Minutes)

While DigitalOcean doesn't have a tutorial for installing Microsoft SQL Server, Microsoft provides a simple quickstart guide for DigitalOcean:

  • , which covers provisioning for AWS, DigitalOcean, and Google Cloud; each of these then link to

Aside: Earlier Versions of Microsoft SQL Server (or Windows-based SQL Installations)

If you're not ready (or licensed) to use SQL Server 2017 or just don't want to run it on Linux, you'll need a Windows instance. Vultr, Google Cloud, and AWS (or Lightsail) all provide these for a marginal additional cost. Some Google-fu will suggest that you can puzzle your way through installing Windows with your own licensing on a DigitalOcean droplet with a custom image. As of April 2019, this is unsupported, but it is possible.

If you can move to SQL Server 2017 (or 2019) for Linux but don't know where to begin, Microsoft provides an

Moving the Default Data, Log, and Master DB Directories

Once you've completed the basic setup guide, you'll want to change the default file directory location for the master database and backup directory location so we can take advantage of block storage. These options (along with several other popular configuration directives) are documented in . Just remember to use the mount point you named in Instance Prep: The guide uses /mnt/db, so if you did the same then you'd use that instead of the example in the Microsoft documentation of /tmp/masterdatabasedir.

Allow Ports 1433 and 1434 through your OS Firewall

Most of our access control will come from the provider-level firewall rather than UFW, so for now we'll just open port 1433 (and port 1434 for the admin console) on UFW and deal with the bulk of the firewall rules in the next section.

sudo ufw allow 1433
sudo ufw allow 1434
Microsoft SQL Server Linux Cloud Install Quickstart
Microsoft SQL Server Ubuntu Quickstart Guide
FAQ for SQL Server on Linux.
Configuring SQL Server on Linux