Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m using entity framework model first development, and I need to do database migration often,
The EF database generation power pack doesn’t help a lot, because that data migration never worked here.
The database migration here I mean, change the model, and then I can update the existing database from the model, but creating a new one.
Is there any free of charge tool here invented here yet? Or would this going to be a new feature of next EF release?
PS: I love django’s ORM.
I use a couple of tools right now for migration, both of EF models and of schemas generated through the NORMA tool. I mostly use the ApexSQL Diff tool, then run the generated scripts through their ApexSQL Edit tool. With the Diff tool, I compare a database created from the model against the “current” database to create a change script. I use the latter because it will break the execution into batches and show the errors on each batch separately (if there are any errors).
On a related note, I’ve been using the ApexSQL Data Diff tool to script changes in base data like lookup tables.
I’ve been intrigued by the Data-Tier Applications feature of Visual Studio 2010 and SQL Server 2008 R2. It seems to store the metadata description of the database to be created, so that when you redeploy the DAC package, it compares the metadata for changes. It then changes only the parts of the database that actually need changing. This should allow a single deployment package to be used to upgrade different revision levels of the database, without the need for individual per-version upgrade scripts. I haven’t yet used that, though, and I believe it’s limited to SQL Server 2008 R2.