Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>You may find my question <a href="https://stackoverflow.com/questions/988426/how-should-you-build-your-database-from-source-control">How Do You Build Your Database From Source Control</a> useful.</p> <p><strong>Fundamentally, effective management of shared resources (like a database) is hard.</strong> It's hard because it requires balancing the needs of multiple people, including other developers, testers, project managers, etc. </p> <p>Often, it's more effective to give individual developers their own sandboxed environment in which they can perform development and unit testing without affecting other developers or testers. This isn't a panacea though, because you now have to provide a mechanism to keep these multiple separate environments in sync with one another over time. You need to make sure that developers have a reasonable way of picking up each other changes (both data, schema, and code). This isn't necesarily easier. A good SCM practice can help, but it still requires a considerable level of cooperation and coordination to pull it off. Not only that, but providing each developer with their own copy of an entire environment can introduce costs for storage, and additional DBA resource to assist in the management and oversight of those environments.</p> <p>Here are some ideas for you to consider:</p> <ol> <li>Create a shared, public "environment whiteboard" (it could be electronic) where developers can easily see which environments are available and who is using them.</li> <li>Identify an individual or group to own database resources. They are responsible for keeping track of environments, and helping resolve the conflicting needs of different groups (developers, testers, etc).</li> <li>If time and budgets allow, consider creating sandbox environments for all of your developers.</li> <li>If you don't already do so, consider separating developer "play areas", from your integration, testing, and acceptance testing environments. </li> <li>Make sure you version control critical database objects - particularly those that change often like triggers, stored procedures, and views. You don't want to lose work if someone overwrites someone else's changes.</li> </ol>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload