Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • 5
    Simply. Don't use production database for development. Create a smaller, sample database for development and testing. Use the production database for performance testing and smoke testing only. Commented Apr 23, 2020 at 8:03
  • In what manner do they step on each other's toes? Change the same entities? Locking queries? Commented Apr 23, 2020 at 21:16
  • An example that comes to mind is a developer changing a stored procedure to work with their code which affects other developer as they are working on there own feature branch but all are pointing to the same DB. Commented Apr 24, 2020 at 9:09