title: Staging database good practices
body: <p>I'm about to deploy to production a fairly complex site and for the first time need a staging environment where I can test things in a more realistic environment, especially with regard to some external services that cannot be run locally.</p>
  
  <p>My general plan is to develop &amp; test first locally, push simple changes (small bug fixes, HTML/CSS, JS, etc) direct to production, and for larger changes, push first to staging subdomain for thorough testing and then to production.</p>
  
  <p>I don't think that I need to keep the staging and production databases in sync (occasional manual updating would do) but I'm wondering if there are any general good practices with regard to maintaing a staging environment in relation to a production environment, especially when it comes to databases.</p>
  
  <p>Any general thoughts/advice/experience would be appreciated.</p>
  
  <p><strong>UPDATE:</strong></p>
  
  <p>Thanks for the comments, I get the gist. I guess it's worth taking some time to think about this. Accepted the popular answer.</p>