Messages

1

Automation Interface, Add-Ins and Tools / Re: Generate separate DDL file for each table

« on: February 28, 2024, 09:11:07 am »

Thanks for the reply, Shimon.
"Add-in" may not be an option for my project.
I'll try if I could write a JS or VB script to get this going.
But would appreciate if someone has already done something similar and can share the code.

Regards,
Arun

 

2

General Board / Re: Attribute/Column lengths from Logical to Physical Data Model

« on: February 21, 2024, 01:12:51 pm »

Thanks Shimon, for your reply.

I kind of worked out on a workaround. I converted a class to a table (and set the DB to SQL Server). Once the class is converted to table, the attributes start to show the lengths and other properties like NULLable too. Defined the lengths and also the NULLABLE property. Once the attribute's properties are set, convert the table back to class.
Even after conversion EA still holds this information which is abstracted.
During physical model transformation, once these classes are transformed into tables, the columns of the tables are created with the lengths as defined in the class's attribute length.
 

3

Automation Interface, Add-Ins and Tools / Generate separate DDL file for each table

« on: February 19, 2024, 11:51:44 am »

Hi all,

I am generating individual DDL script files for each table in my physical data model. But, this options prompts for the table name for each DDL that is being generated.
Can I write a script to automate the process, that is, a script that will take the table name and generate the DDL with same name as that of table? Anyone done it something similar, appreciate your help.

Regards,
Arun 

4

General Board / Attribute/Column lengths from Logical to Physical Data Model

« on: February 07, 2024, 02:49:25 pm »

Hi All,
In logical class model I have defined attributes and they do not have option to define the lengths.
For example, if my class name is Employee and EmployeeName is the attribute defined as VARCHAR, I don't see option to define the length say 100 Characters wide in logical model. I have defined the default database (SQL Server in my case) which has default lengths for each applicable datatypes. for example 50 for varchar, 10 for char, etc.
When I convert the Logical model to Physical, all the varchar attributes are converted to columns in the table as expected, but all are defaulted to a standard size 50.
My question is: Can I define attribute size in logical models? If the answer is NO, then I can define size in converted physical model but how to avoid the size getting overwritten next time?

Regards,
Arun

5

Automation Interface, Add-Ins and Tools / Re: How to transform a logical data model to a physical one

« on: January 18, 2024, 09:42:22 am »

Thank you, Geert. Appreciate your response.

6

Automation Interface, Add-Ins and Tools / Re: How to transform a logical data model to a physical one

« on: January 12, 2024, 05:06:01 pm »

Thanks Matthew, for the steps.
I have followed the same steps and I see a problem. My models(diagrams) are organised in various packages and my models use classes from other packages. Thus, when I transform I don't see those classes and thus the tables are not generated. Any work around that you could suggest?

And one more issue that I face is, how do I inherit the attributes in tables. What I mean is, I have class A and Class B, class B is inherited from Class A. When I transform, I get Table A and Table B, but Table B does not have the attributes from Table A, I thought that Table B will include all the attributes from Table A and will also contain its own attributes. Any setting that I need to turn On or Off?

7

Automation Interface, Add-Ins and Tools / Re: Report only features that are visible on diagram

« on: January 10, 2024, 03:58:30 pm »

You can write a macro in excel to read the class and its various properties from the diagram that is open (Active diagram) or open the desired diagram and loop through the classes / objects within the diagram to capture the information in excel spreadsheet. Let me know if that is what you are looking for and I can share the code snippet.

Regards,
Arun

8

Automation Interface, Add-Ins and Tools / Re: How to transform a logical data model to a physical one

« on: January 10, 2024, 03:49:31 pm »

Thanks for the suggestion Geert.

I eventually found out how to do it. As my logical model was done as Classes representing the entities, the standard 'ERD to Data Model' transformation wouldn't work. After much digging around, and help from a colleague, I used the 'Tables' transformation and this did what I expected - took the Platform Independent logical model classes and converted these into new DB-specific entities (SQL Server in my case) and created links back from the generated objects to the source logical model objects.

But my word, it shouldn't have taken so long to find out how to do this - if only the help files went from 'you can do transformations' to actually showing you what you had to do to perform it, that would save so much time !

Hopefully this thread will help someone else in the future.

Hi Ducatiross,
I have a UML class diagram model, I now want to create a physical data model (DB being SQL Server). Could you point me to some resources on how you managed to create this. I wanted the physical model tables pointing back to the logical data model classes like you mentioned. Thanks in advance.

Regards,
Arun