Answers: <p>Docker is an awesome tool for creating a database, seeding data into it, and disposing of it.</p>
  
  <p>For an example check out <a href="https://docs.microsoft.com/en-us/sql/linux/quickstart-install-connect-docker?view=sql-server-2017&amp;pivots=cs1-bash" rel="nofollow noreferrer">Microsoft's SQL Server with Docker</a>.  The following would pull and run a sql server 2017 instance: <pre><code>docker run -e "ACCEPT_EULA=Y" -e "SA_PASSWORD=" 
     -p 1433:1433 --name sql1</code>
     -d mcr.microsoft.com/mssql/server:2017-latest</pre>After running this you now have a developer ready SQL instance that you can then connect to SQL Management Studio (or any other GUI management tool), or you can even connect via the <a href="https://docs.microsoft.com/en-us/sql/linux/quickstart-install-connect-docker?view=sql-server-2017&amp;pivots=cs1-powershell#connect-to-sql-server" rel="nofollow noreferrer">command line</a>.</p>
  
  <p>If you are not using SQL you can run a container for the desired database type (check out the options on Dockerhub).</p>
  
  <p>Once you have your database up and running, run the scripts to set it up, seed the data, and test without worrying about messing up your production database.</p>
  
Answers: CC BY-SA 4.0
Answers: 2019-10-31T18:21:36.800Z
Answers: Thank you! Would it be possible to set up our own container image remotely that is the most up to date version that all the developers could then pull from and test against?
Answers: avenmia
Answers: CC BY-SA 4.0
Answers: 2019-10-31T19:56:47.443Z
Answers: Yes.  You can create an image for the team and have everyone pull that from a repository you push it into.
Answers: Wesley Rolnick
Answers: CC BY-SA 4.0
Answers: 2019-10-31T17:42:44.950Z
Answers: 2019-10-31T17:42:44.950Z
Answers: Wesley Rolnick
Body: <p>I'm currently working at a small company where we've had a lot of issues being on the same page with entity framework migrations and local databases. I want to start incorporating containers in hopes of standardizing everyone's development environment. Ideally, I'd like a disposable database that can be modeled using Entity Framework code first, seed data into it, then disposed of once the testing is done. What resources are there to help get me started and what other things should I know about standardizing the development environment.</p>
  
Comments: CC BY-SA 4.0
Comments: 2019-10-31T17:29:58.750Z
Comments: What type of environment are you developing within? i.e. which Operating Systems do developers use? what is the database software in use - MSSQL, MySQL, PostgreSQL?
Comments: Richard Slater
Comments: CC BY-SA 4.0
Comments: 2019-10-31T18:20:02.097Z
Comments: The dev environment is a windows 2016 server vm because the application requires sharepoint 2016. We're using MSSQL for the database with Visual Studio 2019 as the IDE. The developers working on this are all using Windows 10.
Comments: avenmia
Comments: CC BY-SA 4.0
Comments: 2019-10-31T18:36:24.230Z
Comments: Are you wanting to run SharePoint in the Docker-ised Dev environment?
Comments: Richard Slater
Comments: CC BY-SA 4.0
Comments: 2019-10-31T18:38:52.960Z
Comments: I'm more focused on the database being containerized for now, but if there was a way to also run sharepoint in the docker-ised environment as well that would be cool. I'm not sure how I would get started with that yet though.
Comments: avenmia
Comments: CC BY-SA 4.0
Comments: 2019-10-31T18:40:31.110Z
Comments: I assume by that it means your not developing WebParts?
Comments: Richard Slater
Comments: CC BY-SA 4.0
Comments: 2019-10-31T18:50:33.150Z
Comments: Sorry, what are WebParts? I don't believe so. We're migrating our sharepoint application to utilize sql server to handle data instead of using sharepoint lists.
Comments: avenmia
Comments: CC BY-SA 4.0
Comments: 2019-10-31T18:52:22.987Z
Comments: SharePoint components, given everything you have told me it looks like @Wesley Rolnick’s answer would get you started.
Comments: Richard Slater
Tags: <docker><databases><sql>
Title: How to incorporate containers into a standardized dev environment?
UserDisplayName: avenmia
ThreadText: # How to incorporate containers into a standardized dev environment?
  
  (Asked by: username_0 on 2019-10-31)
  
  I'm currently working at a small company where we've had a lot of issues being on the same page with entity framework migrations and local databases. I want to start incorporating containers in hopes of standardizing everyone's development environment. Ideally, I'd like a disposable database that can be modeled using Entity Framework code first, seed data into it, then disposed of once the testing is done. What resources are there to help get me started and what other things should I know about standardizing the development environment.
  
  **Tags:** docker, databases, sql
  
  > **Comments:**
  > **username_1**: What type of environment are you developing within? i.e. which Operating Systems do developers use? what is the database software in use - MSSQL, MySQL, PostgreSQL?  
  > **username_0**: The dev environment is a windows 2016 server vm because the application requires sharepoint 2016. We're using MSSQL for the database with Visual Studio 2019 as the IDE. The developers working on this are all using Windows 10.  
  > **username_1**: Are you wanting to run SharePoint in the Docker-ised Dev environment?  
  > **username_0**: I'm more focused on the database being containerized for now, but if there was a way to also run sharepoint in the docker-ised environment as well that would be cool. I'm not sure how I would get started with that yet though.  
  > **username_1**: I assume by that it means your not developing WebParts?  
  > **username_0**: Sorry, what are WebParts? I don't believe so. We're migrating our sharepoint application to utilize sql server to handle data instead of using sharepoint lists.  
  > **username_1**: SharePoint components, given everything you have told me it looks like @username_2’s answer would get you started.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2019-10-31. Score: 1 | Accepted answer
  
  Docker is an awesome tool for creating a database, seeding data into it, and disposing of it.
  
  For an example check out [Microsoft's SQL Server with Docker](https://docs.microsoft.com/en-us/sql/linux/quickstart-install-connect-docker?view=sql-server-2017&pivots=cs1-bash). The following would pull and run a sql server 2017 instance:
  
  ```
  docker run -e "ACCEPT_EULA=Y" -e "SA_PASSWORD=" 
     -p 1433:1433 --name sql1
     -d mcr.microsoft.com/mssql/server:2017-latest
  ```
  
  After running this you now have a developer ready SQL instance that you can then connect to SQL Management Studio (or any other GUI management tool), or you can even connect via the [command line](https://docs.microsoft.com/en-us/sql/linux/quickstart-install-connect-docker?view=sql-server-2017&pivots=cs1-powershell#connect-to-sql-server).
  
  If you are not using SQL you can run a container for the desired database type (check out the options on Dockerhub).
  
  Once you have your database up and running, run the scripts to set it up, seed the data, and test without worrying about messing up your production database.
  
  > **Comments:**
  > **username_0**: Thank you! Would it be possible to set up our own container image remotely that is the most up to date version that all the developers could then pull from and test against?  
  > **username_2**: Yes.  You can create an image for the team and have everyone pull that from a repository you push it into.  
  
  ---
  
  