Author: Kovid Rathee

Kovid is a Data & Infrastructure Engineer working as a Senior Consultant at Servian in Melbourne, Australia. He is originally from Rohtak, India. In a career spanning 10 years, he has worked for startups and corporates, product companies and service companies alike. He started his career as an Assistant Professor at an engineering college and later moved to a full stack developer role for a while, before finally moving into the data space where he has been working for the past 8 years. He likes to write about data engineering, infrastructure-as-code, DevOps and SRE. He is a semi-trained Indian classical singer, writes poetry in Hindi and Urdu, and hopes to get published someday.

How to Collaborate Effectively in Vertabelo

Learn how to use Vertabelo's features to collaborate effectively on database models and documents. In the post-pandemic world, effective collaboration on database modeling is of the essence. Database developers and data modelers must work together on developing data models and writing SQL queries, functions, procedures, and more. Every substrate of software engineering is becoming more collaborative by the day, and database development is no different. Teams cannot function properly to deliver results if they are not using the right tools.

What Are Document Types in Vertabelo?

Create logical data model documents, physical data model documents, and SQL script documents using Vertabelo. Vertabelo allows you to create and import your models with three different types of documents. This article takes you through all three Vertabelo document types: the logical data model, the physical data model, and the SQL script. These documents let you start modeling from scratch or import your existing progress into Vertabelo. The different representations of the same data model help a variety of people understand the model.

7 Tips for a Good ER Diagram Layout

In this article, you will learn some practical tips for organizing data models, creating readable layouts, and efficiently working with ERDs (entity-relationship diagrams). Database diagrams are to applications what blueprints are to buildings. The more components a building has, the more complicated it is to design. Unlike buildings, though, databases undergo persistent changes, which is why ER diagrams are used to understand the structure of the database and ensure that the most current models are deployed.

Our website uses cookies. By using this website, you agree to their use in accordance with the browser settings. You can modify your browser settings on your own. For more information see our Privacy Policy.