- ALWAYS have a local database. No dependencies on remote database where other people are changing data, changing tables, etc. - Make sure there is a create sc

- ALWAYS have a local database. No dependencies on remote database where other people are changing data, changing tables, etc. - Make sure there is a create script with change scripts checked into source control that brings your local database to the latest state. For ASP.NET specifically I use a database project which contains XML files that describe the state of the database. You can then just use the compare tool to bring your own DB up to the same state, and reversely you can merge changes in your own DB back to the database project to deploy to other people. - Every developer can fill his local database with his own database. Whatever that may be.