They send us data sets and we can reverse-engineer what they send us, especially the backup snapshots where a vendor in the cloud will send data as a backup restore. We also do reverse-engineering where we are capturing the catalogs of existing systems, or purchased software, or even external vendor datasets. They're only about datasets, the owned attribution, and different key analyses to determine what primary keys we want.Īnd then we do database designs, which relates to the physical data models. Then we do logical data models, which are completely platform-independent.
It helps us to do a scope statement at the beginning of a project to corral what the area is that the data is going to be using. We can then use the graphic interface to create boxes that contain descriptions of things and connect things together. It's more concepts that the business described to us in words. We do conceptual data modeling, which is very high-level and doesn't have columns and tables. We use erwin Data Modeler to do all of the levels of analysis that a data architect does. You can have two models, one in English and one in Japanese, but that means you have to keep the updates back and forth, and that always increases the risk of something not being updated."Įrwin Data Modeler does conceptual, logical, and physical database or data structure capture and design, and creates a library of such things. When I was working at Honda, it became very difficult to work with the Japanese teams using just one model. "One of the things I've been talking to the erwin team about through the years is that every data model should have the ability to be multi-language.You can go back to a different version or connect that to your change-control processes so you can see what was released when." If you're looking at a specific database and you want to see what changed over time, that's really useful. "erwin has versioning so you can keep versions, over time, of those models and you can compare any version to any version.Visio isn't going to reverse-engineer that for you. "When you're getting down to the database level, where you're building a design and you're creating DDL out of it, or you're going in the other direction where you're reaching into system catalogs and bringing things back, that starts to really require specialization.Concurrent licenses are scalable to the number of users and are proportional to the cost."
#Ca erwin data modeler version history license#
There is something called concurrent licenses where you can purchase licenses in bulk and 15 to 20 people can access the license and model. While you can buy a license for each individual, that would be very expensive.
I would love to personally buy a copy of my own and have it at home, because the next job that I'm looking at is probably project management and I might not have access to the tool. I haven't talked to erwin people yet, but I'm going to suggest to them that they could perhaps think of having an entry-level product that is priced a bit lower, and then, you can buy the extra suite." I get the impression that there was a price jump when it was spun off from CA as a separate company, which is understandable, but it could sometimes be a barrier in some organizations picking it up. In the mid-2000s, it was something like 1,200 AUD a seat. About three years ago, in another organization, I have this memory of 6,000 AUD a seat or something like that, but I am not sure. "I don't specifically know what we're paying now."The primary reasons that erwin was selected were that it was much more affordable for us and it was easily maintainable.".
0 kommentar(er)
