title: Whats the use of Migration History in Code First Migrations
body: <p>I'm getting the "The model backing the context has changed since the database was created" when I deploy to my code to the test environment.  The database was created by running the script output from <code>update-database -script</code> on the database.  So it originally had the Migration History table with the same values as my development database server.  There is quite a lot of discussion around this already - most of it suggesting simply dropping the table.  So I've dropped it and everything is fine.</p>
  
  <p>But is it?  Is that really the idea?  Or am I likely not using the migrations right?  I've not posted any code because I'm not sure what would help you the most.</p>
  
  <p>EDIT: I'll put this another way?  I generated the sql script from the console inside VS while pointing at my local SQL Express.  I've taken that exact script (including the migration history table and insert at the end) and run it on an entirely new database server (test).  I've released my website code to the matching test web server, and I get the error.  Is this the way migrations are supposed to be used?</p>