The route that you took is an initialization strategy, and it is behaving in the expected manner. You don't want to use it for a production database, what you'll want to use instead is a Migration.
Code First migrations are described in detail at:
http://msdn.microsoft.com/en-us/data/jj591621.aspx[
^]
You can also write your own initialize, but I would not go down that route unless you want to start getting into the weeds of how EF interacts with the database.
The most important lesson here: migrations != initialization strategy