On my local development server I have a database set up which gets hooked into Entity-Framework and is then used for unit testing. Let's call it
On the same server (and same database instance) I then have another database -
COMPANY\DatabaseStaging which has the exact same structure but persistent test data used for constructing a front end site around.
So, to hopefully clarify, the structure/flow is something like:
Create or modify a table:
Update entity framework, write some business logic, unit tests, etc against the table.
Manually mirror/replicate the changes:
Put in some slightly more persistent test data and do front end/ASP.NET stuff.
Now, this doesn't seem very elegant to be manually updating the
COMPANY\DatabaseStaging database to make it reflect changes in
COMPANY\Database. Is there a better way of doing it?