Under review

Copy and paste columns

Oggy Shopov 3 years ago • updated by Sergio Sardo 3 weeks ago 12
It would be very convenient if one or more columns can be selected from one table and then pasted into another table along wit all of their settings. Many companies have audit trail policies for their data, which means all of their entities have a number of columns for CreatedBy, CreatedOn, CreatedIpAddress,  ModifiedBy, ModifiedOn, ModifiedIpAddress, ActiveRecord, etc. As you can see that's a lot of columns with identical settings, but it is time consuming to create them on each table.
Thank you.
Under review
It seems useful and interesting. We have to think how to this from UX perspective.

I keep this issue opened to allow other users to comment.
I want to copy columns too. Right now, I have to copy and edit a table to save these settings.
Absolutely the most noticeable missing feature, to me. A big +1

Would be nice to be able to copy between models in same manner (including entire table, selection of tables, or an area). Currently only way I see of doing this would be xml export, modify, import.

Would be nice to be able to copy between models in same manner (including entire table, selection of tables, or an area).

Copy&paste of selected diagram objects is possible. You can just select some tables/views/references/areas, copy them, switch to a different model and paste right there. It should work.

In case of copy&paste of columns, we don't support it yet. Looking at the number of upvotes, I'm pretty sure we will do this.

Hi! I recommend you reading our 24 tips for Vertabelo users. There's a lot of interesting tricks there, including copying and pasting tables between two models:


This is copying/pasting columns, not tables. This is available in the top 3 data modeling products -- visual column select (one or many), copy, and paste.  In PowerDesigner, they allow CUT and paste, only, so you copy/paste a table, move the columns with click&drag to the target table.

Alternatively, for Audit columns, ER-Studio has a macro feature that allows one to define a standard set of audit columns and add them to all tables as part of DDL generation, so that the Logical Data Model is not "polluted" with a stack of physical-only attributes that make for a far less-business-friendly model display.


+1! Working with large database needs to adopt and follow some standards, includedcolumn names, size, types, ... This would-be feature can really leverage the -already rather good- Vertabelo quality and usability

For the record, these are the sorts of additional features that make a nice quick-and-easy modeling tool into an enterprise class tool. (That and a repository with version control, but that's a huge ask).