1
In the company I work have chosen to create the models from the database with the Entity Power Tools
.
We have an online version of our application and locations for testing and development.
When necessary to change something in the models, we change in the bank and generate the models again... so far so good, we use versioning and everyone gets the same models.
The problem is bank changes, for example:
A VALOR_NOTA field was double now became decimal
Dai we have to make this change in the SQL of all machines.
There is a way to versioning the structure of a table in SQL Server?
It’s not easier for you to use Migrations? Then the database versioning is in the application code.
– Leonel Sanches da Silva
I already suggested with research and evidence, accepted the tip but only after the finalizing of the prospectus. So I will have to wait!
– Trxplz0
Look, there is. The problem is mapping these structural changes. About 5 years ago I wrote a tool in Python that read an SVN repository with the structure and generated the change of version scripts, but it was a lot of work and it was very time consuming. We versioned SQL scripts with the table declaration. That’s what we could do.
– Leonel Sanches da Silva
um... good idea, da para colocar as declarações em um SQL e Versionar dai eu crio uma macro para executar elas a clique já ajuda me! I’ll wait someone might know a way... in case no one shows up as I should close the question?
– Trxplz0
I answer to you. I just wanted to validate some things.
– Leonel Sanches da Silva
@Ciganomorrisonmendez how do I move this conversation to a chat? I would like to ask a few questions about Migrations if possible!
– Trxplz0
Let’s go continue this discussão in chat.
– Leonel Sanches da Silva