Your feedback is highly appreciated! Let's make Vertabelo even better.
Whenever you do a model migration on a SQL Server Physical Model, it forgets to add the schema to the first mentioned table. Should be an easy fix.
When creating our databases with thousands of fields we use domains / user data types. This allows us to use a specific defined data type, like "ID Key" for all primary keys, to ensure they are all uniformly the same data type. Additionally it would allow us to change the data types of all the fields that would apply without having to go to each field manually and changing it. This is a must for us to purchase a database modeling product.
Hi there, I am trying to import an xml file that I created using the Vertabelo Reverse Engineering tool. However, when I try to import it, nothing seems to happen when I click the import button.
The file is rather large, the database that I reverse engineered it from has 600+ tables with 10000+ columns, 600+ views and 1000+ references resulting in an xml file of ~17MB.
I reverse engineered a subset of tables from the same database giving a much smaller file and that imported with no problems so I'm wondering if it is a size issue. Is there a maximum allowed size of the import file?
We have increased the limit to 30MB.
Please try again.
Could you please evaluate to allow export and import logical and physical data model via csv?
When we design a data model we map all the entities and attributes using Excel (specially for LOGICAL model), in vertabelo the only option to import logical and physical is using xml file.
Is it possible to show on physical diagram only the primary key and foreign key attributes?
I have a big model and showing all the attributes from the diagram it is not readable, does exits the functionality to show only PK and FK?
Grid functionality has been alredy introduced. You can find this feature in Format tab of Model properties (right panel) as shown on the following screenshot.
Customer support service by UserEcho