How one of the largiest Slovenian companies benefited from the shift to a new ERD tool

The decision to ditch the former ERD tools for all those involved was not something that needed much thought because of the many benefits that came with SqlDBM. It’s important that we’re talking about SaaS technology here, which is very much needed in the growing cloud environments.

With some of the former solutions it was a painful process just to extend the licenses and there was a waiting period of up to two weeks before the license was valid again. Who would want that? We need to mention here that both former solutions we used are well known, respected and widely used data modellers. Needles to say that this does not come without an expensive price tag.

Now that we have this tool available online, any member of the team can access the project. ZERO management, no sync, no waiting times. Simply sign in and see the up to date, real time situation. SqlDBM solution eliminated many administration tasks for Amir and his team. The minute somebody works on it, anybody who is part of project sees the final picture. A small price to pay for getting something so valuable out of it – especially when compared to the previous situation. Our next point describes how all of this is made possible.

One of the things we really appreciate about the SqlDBM team is that they are genuinely interested in what their users have to say. You see that in the constant improvements that make your job easier. And the Team project collaboration is one of them.

Let’s say you have a project you’re working on available online – you can create team members and assign them roles. These can access the project whenever, wherever. Every member of the projects has the same view, everybody is working on a unified methodology and anyone who ‘checks-in’ has the latest info. The up to date diagram is now always available for everyone involved. Team collaboration was, for us, one of the strongest features that made our work a whole lot easier.

Team members can have permissions to ‘Edit’ or you can allow them to ‘Read only’. This is useful when you want a department to check on the situation regularly in order to be up to date but you don’t want them to mess with it. This is why the BI department at Petrol have the viewer roles without editing rights. However, they could still play around with the diagram in order to discover interesting viewpoints, take a screenshot and send it to the development team to try out their version.

Furthermore, every time somebody saves their work, a new version is created, and each version can be addressed with a label or comment. Any member can go back as many steps as they want to in order to see the former versions and are able to see who changed what. Somebody messed things up or is the current version not something you hoped for? No problem, you can always go back as many versions you’d like and re-start from there. And don’t worry – while one of the members is editing the diagram, no one else can until they are done.

On DWH projects we usually have at least two environments – i.e. one for production and the other for testing and development. We find it very helpful to have an instant view of both environments so that we can easily compare the two. Once you create a desired development structure, you can easily integrate the changes to the production environment. All you need to do is to deploy the Alter scripts to production instead of rewriting the logic.

The ability to reverse engineer was a very practical thing to have, since Petrol didn’t start their DWH from scratch. In such cases, this feature is very practical. Simply import the existing model into SqlDBM, which is then built automatically and you can immediately start with forward engineering.

Later on, once all the complexities and details are decided, you can simply generate all the necessary SQL statements that are needed to build your DB/DWH.