title: SQL Server database keeps setting SINGLE_USER on in tests
body: <p>I have 2 docker containers that host their own server. I also have a 3rd docker container that hosts a SQL Server database. Each server accesses this database.</p>
  
  <p>My DB docker container is configured as so in the docker-compose.yml:</p>
  
  <pre><code>my-db:
       image: microsoft/mssql-server-linux:latest
       environment:
         - ACCEPT_EULA=Y
         - SA_PASSWORD=******
       ports:
         - "1433:1433"
  </code></pre>
  
  <p>Each servers connection string (They are .NET servers) are </p>
  
  <pre><code>ConnectionStrings__Default=data source=my-db;initial catalog=TestDb;persist security info=True;user id=SA;password=******;
  </code></pre>
  
  <p>When I run my tests, I get a log from the docker container for the DB that says it's setting SINGLE_USER mode on. This obviously breaks my tests because both servers have to access it.</p>
  
  <p>I tried using a DB browser to set MULTI_USER on which worked... until the tests started... Then the db or something in the test suite switched it back to SINGLE_USER.</p>
  
  <p>How do I configure this through the docker compose, dockerfiles or anything else to NOT set SINGLE_USER mode on or specifically set MULTI_USER mode on?</p>
  
  <p>In case it matters: I'm also using Selenium for tests and circleci for test automation.</p>