Tag Info

New answers tagged

0

The simple answer is don't use Entity Framework for this sort of thing. You need to write a SQL migration script, test it, and then deploy it onto your production system. And yes - changing a table with 3M rows will take more time and resources than migrating a table with 3 rows. There are a few techniques for achieving this. First, judging by the error ...



Top 50 recent answers are included