SQL Datamodeler: engineer to relational model: column names

Hello
Suppose I have an attribute called DAY OF BIRTH. Is there a way I can forward engineer this attribute to a column name DAY_OF_BIRTH?
(I know you could have a coulmn name "day of birth" but thats not what I want)
Regards Erik

Hi Erik,
1) you should check separator settings in General options>Naming Standard -it should be "space" for Logical model and "underscore" for Relational model;
2) "Apply name translation" should be selected in engineering dialog
Best regards,
Philip

Similar Messages

Sql datamodeler: Engineer to relational model: General Options

Hello
When you engineer your logical model to a relational model you get a wizard. In lower part of this wizard byou have several tabs, one of the tabs is called general.
On this general tab you have check box: Apply Name Translation
The corresponding help text:
Apply Name Translation: Controls whether formal names are translated to abbreviated names when the logical model is forward engineered to a relational model, and whether abbreviated names are translated to format names when a relational model is reverse engineered to the logical model. Name translation is applied only for valid names. In addition, translations between the words entity/attribute/key and table/column/index are performed.
Does anybody have a clue what is meant here?
Regards Erik

Erik,
you have to create glossary (tools>Glossary editor) with words permitted for usage in names in logical model. For each word you can define abbreviation that will be used in transformation process.
Example:
Employee - EMP
Salary - SAL
Attribute "Employee Salary" will be transformed to column "EMP_SAL".
You can define preferred abbreviation for entities and attributes and it can be used instead of glossary definitions.
You also have to set your glossary in "Tools>General Options>Naming standards>Glossary"
Best regards,
Philip

Sql datamodeler: Engineer to relational model

Hello
is it possible to add a prefix to all your tables?
Suppose I have entities A, B and C
Than I would like to have the following tables as a result
XYZ_AS, XYZ_BS and XYZ_CS
This according to the CDM standards
Regards Erik

Erik,
it's possible to replace one prefix with another one in current published build (525). It'll be possible to add (replace) prefix to all tables or to tables in certain subview in next release. There won't be possibility to change name A to name XYZ_AS; there will be no problem to change names A and B to XYZ_A and XYZ_B.
Best regards,
Philip

Engineer to Relational Model: deleted attributes / undeleted columns

Hello,
I am using Datamodeler 3.3.0.744.
I'm modifying an existing logical model: I'm deleting one or more attributes in an Entity.
Then I'm executing "Engineer to Relational Model" in oder to get an up to date Relational Model (it existed already).
The corresponding columns are not deleted in the Relational Model, even though attributes don't exist anymore at the logical level.
I can't find any option available in order to do that...
In the previous release (3.1), it worked fine, I could choose the behavior related to the deleted attributes (deleting or not deleting corresponding columns).
Edited by: user4995029 on 27 mai 2013 02:43

When your forward engineer for a 2nd time you should see a dialog that has the logical on the left and the relational on the right. Entities that are new or changes have an exclamation point next to them. If you open that you will eventually drill down to see the attribute/columns. Where your dropped an attribute it will say "To drop". The check box is unchecked by default. If you check it then when you forward engineer those should get dropped from the associated table.
Is it not working that way in 3.3?

'Engineer to Relational Model' Dialog does not open

Steps to reproduce:
Open Modeler.
Create a Glossary file with one row as ATTRIBUTE & ATTR as Name & Abbreviation respectively. Check "Incomplete modifier".
Goto Naming standards under preferences, choose that glossary file. In the logical model, create an entity with one attribute "ATTRIBUTE 1".
Right click logical model, click 'Engineer to Relational Model', goto General Options tab, check "Apply Name translation". Click Engineer.
You'll see ATTRIBUTE is not changed to ATTR in the relational model.
Now right click logical model again, click 'Engineer to Relational Model'. Nothing happens now.
Goto Naming standards under preferences, double click the glossary file, uncheck Incomplete modifier", save & close.
Now right click logical model again, click 'Engineer to Relational Model'. It works now. But still the abbreviation does not happen in the relational model.

Sorry for the very late reply.
My version is this -
Version 3.1.0.700
Build 700
And my fresh log file is below (it shows an error. but I dont think that is related with the problem that I am having now)
2012-06-26 05:59:44,639 [main] INFO ApplicationView - Oracle SQL Developer Data Modeler 3.1.0.700
2012-06-26 06:00:12,440 [Thread-13] ERROR XMLTransformationManager - Unable to load object from XML: D:\Lenin\CODE EU\Adhoc Subject Wise\mapping\ExtendedMap_RM6FC65D48-B203-C5D5-5BDE-6BF8B4199E5A.xml
java.io.FileNotFoundException: D:\Lenin\CODE EU\Adhoc Subject Wise\mapping\ExtendedMap_RM6FC65D48-B203-C5D5-5BDE-6BF8B4199E5A.xml (The system cannot find the file specified)
     at java.io.FileInputStream.open(Native Method)
     at java.io.FileInputStream.<init>(FileInputStream.java:106)
     at oracle.dbtools.crest.model.metadata.XMLToObjectTransformer.transformToObject(Unknown Source)
     at oracle.dbtools.crest.model.metadata.XMLToObjectTransformer.transformToObject(Unknown Source)
     at oracle.dbtools.crest.model.metadata.XMLTransformationManager.transformFromXMLToObject(Unknown Source)
     at oracle.dbtools.crest.model.metadata.XMLTransformationManager.transformFromXMLToObject(Unknown Source)
     at oracle.dbtools.crest.model.design.Design.openDesign(Unknown Source)
     at oracle.dbtools.crest.swingui.ControllerApplication$1.run(Unknown Source)
UPDATE:
I have downloaded the latest version (Version 3.1.1.703 Build 703) and opened my model.
Now I am not able to engineer to relation model in any option (tried checked and unchecked "incomplete modifiers")
When I right click logical model and click engineer to relation model, I get an empty dialog box with a warning icon and a OK button - but no message in it.
Here is my log file:
2012-06-26 07:02:48,643 [main] INFO ApplicationView - Oracle SQL Developer Data Modeler 3.1.1.703
2012-06-26 07:03:22,288 [Thread-14] ERROR XMLTransformationManager - Unable to load object from XML: D:\Lenin\CODE EU\Adhoc Subject Wise\mapping\ExtendedMap_RM6FC65D48-B203-C5D5-5BDE-6BF8B4199E5A.xml
java.io.FileNotFoundException: D:\Lenin\CODE EU\Adhoc Subject Wise\mapping\ExtendedMap_RM6FC65D48-B203-C5D5-5BDE-6BF8B4199E5A.xml (The system cannot find the file specified)
     at java.io.FileInputStream.open(Native Method)
     at java.io.FileInputStream.<init>(FileInputStream.java:106)
     at oracle.dbtools.crest.model.metadata.XMLToObjectTransformer.transformToObject(Unknown Source)
     at oracle.dbtools.crest.model.metadata.XMLToObjectTransformer.transformToObject(Unknown Source)
     at oracle.dbtools.crest.model.metadata.XMLTransformationManager.transformFromXMLToObject(Unknown Source)
     at oracle.dbtools.crest.model.metadata.XMLTransformationManager.transformFromXMLToObject(Unknown Source)
     at oracle.dbtools.crest.model.design.Design.openDesign(Unknown Source)
     at oracle.dbtools.crest.swingui.ControllerApplication$1.run(Unknown Source)
2012-06-26 07:03:22,482 [Thread-14] ERROR XMLTransformationManager - Unable to load object from XML: D:\Lenin\CODE EU\Adhoc Subject Wise\mapping\ExtendedMap_RMED70BF0B-C36C-7627-EDDD-1F53A7EAF80F.xml
java.io.FileNotFoundException: D:\Lenin\CODE EU\Adhoc Subject Wise\mapping\ExtendedMap_RMED70BF0B-C36C-7627-EDDD-1F53A7EAF80F.xml (The system cannot find the file specified)
     at java.io.FileInputStream.open(Native Method)
     at java.io.FileInputStream.<init>(FileInputStream.java:106)
     at oracle.dbtools.crest.model.metadata.XMLToObjectTransformer.transformToObject(Unknown Source)
     at oracle.dbtools.crest.model.metadata.XMLToObjectTransformer.transformToObject(Unknown Source)
     at oracle.dbtools.crest.model.metadata.XMLTransformationManager.transformFromXMLToObject(Unknown Source)
     at oracle.dbtools.crest.model.metadata.XMLTransformationManager.transformFromXMLToObject(Unknown Source)
     at oracle.dbtools.crest.model.design.Design.openDesign(Unknown Source)
     at oracle.dbtools.crest.swingui.ControllerApplication$1.run(Unknown Source)
Edited by: emaillenin on Jun 26, 2012 4:36 AM

Engineer to Relational Model - subtypes have no attributes.

Hello.
Engineer to Relational Model tool don`t show attributes of subtype entity. Some bug or feature?
DM 3.1.0.687.

1) Funny, when I dropped the column, and had it recreated by the engineering process, it worked correctly. But re-engineering the old column kept setting it to mandatory even when I manually set it to optional. I have a sense that some of my objects are ignored by the tool... Only when I drop them and recreate them they seem to be recognized. I had the same issue with some entities that consistenetly did not got engineered into my relational model. Only when I created a new ER-diagram and included the same entities they would get engineered into the relational model...
2) Designer did this. When a supertype table was generated in the "one table" mode there would always be a new column called SUBTYPE with a constraint allowing the short names of each subtype as values (ex: for the table PARTIES the SUBTYPE column could only contain the values PERS and ORG). With this in place you could create constraints such as "SUBTYPE = 'PERS' and FIRST_NAME is not null or SUBTYPE = 'ORG' and FIRST_NAME is null".
Regards,
Marc de Oliveira

Syntax of DDL options and related (table) column names

Hi,
where can I find something like a mapping between DDL options and related table column names?
For example I do have the table options PCTFREE, FREELISTS and NOCOMPRESS. The related table columns out of user_tables are PCT_FREE, FREELIST and COMPRESS.
PCT(_)FREE wins an Underscore, FREELIST(S) wins an "S" and it is "NOCOMPRESS" if COMPRESS has a value "Y(es)".
Hope somebody can help.

So far I didn't find any information that is not in
the DDL script gernerated from
DBMS_METADATA.get_DDL.Alright, I give you an example:
I create a table with the following DDL:
"CREATE TABLE IntBuch (
int_bunr integer NOT NULL,
int_sdat double precision NOT NULL,
int_hblz char(8) NOT NULL,
int_hkto char(7) NOT NULL,
int_hdat double precision NOT NULL,
KtoNr char(7) NOT NULL,
BLZ char(8) NOT NULL,
CONSTRAINT PK_IntBuch PRIMARY KEY (int_bunr)
USING INDEX
PCTFREE 10
STORAGE (
INITIAL 1000
NEXT 500
PCTINCREASE 0
MINEXTENTS 1
MAXEXTENTS 4096
PCTFREE 20
LOGGING
CREATE UNIQUE INDEX intid
ON IntBuch (int_bunr DESC)
CREATE INDEX hkto
ON IntBuch (int_hblz,int_hkto)
COMMENT ON TABLE IntBuch
IS 'Kommentar zu DB-Tabelle InBuch'
COMMENT ON COLUMN IntBuch.int_sdat IS 'Kommentar zu DB-Spalte int_sdat'
ALTER TABLE IntBuch
ADD CONSTRAINT Gutschrift FOREIGN KEY (int_hkto,int_hblz) REFERENCES Konto
ON DELETE CASCADE
ADD FOREIGN KEY (KtoNr,BLZ) REFERENCES Konto
ADD FOREIGN KEY (int_bunr) REFERENCES Buchung
ON DELETE CASCADE
After that I read the DDL with DBMS_METADATA.get_DDL and I get
" CREATE TABLE "UOENDE"."INTBUCH"
(     "INT_BUNR" NUMBER(*,0) NOT NULL ENABLE,
     "INT_SDAT" FLOAT(126) NOT NULL ENABLE,
     "INT_HBLZ" CHAR(8) NOT NULL ENABLE,
     "INT_HKTO" CHAR(7) NOT NULL ENABLE,
     "INT_HDAT" FLOAT(126) NOT NULL ENABLE,
     "KTONR" CHAR(7) NOT NULL ENABLE,
     "BLZ" CHAR(8) NOT NULL ENABLE,
     CONSTRAINT "PK_INTBUCH" PRIMARY KEY ("INT_BUNR")
USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 16384 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "USERS" ENABLE,
     CONSTRAINT "GUTSCHRIFT" FOREIGN KEY ("INT_HKTO", "INT_HBLZ")
     REFERENCES "UOENDE"."KONTO" ("KTONR", "BLZ") ON DELETE CASCADE ENABLE,
     FOREIGN KEY ("KTONR", "BLZ")
     REFERENCES "UOENDE"."KONTO" ("KTONR", "BLZ") ENABLE,
     FOREIGN KEY ("INT_BUNR")
     REFERENCES "UOENDE"."BUCHUNG" ("BU_NR") ON DELETE CASCADE ENABLE
) PCTFREE 20 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "USERS"
If there are no more DDLOptions possible than that, it is fine for me. If not, but all kinds of options are to find in only one or two tables of the database ( user_tables for table options, dba_constraints and dba_segments for column options, primary and foreign keys, user_indexes and user_segments for indexes ...), that is fine for me, too. (As long as I get to know which tables are "sufficient" for that.) If it is different than both of that, that's bad.
However if you want to use defaults instead of
absolut values, it is better to remove certain parts,
like the storage clause, from the generated output.I understand this, but I am more interested to have all and not leaving out some of them in order to have the defaults in the database after running the DDL.
A totally different approach could be to
a) create a database link from one DB to another.
b) create table <new_table> as select * from
<old_table@dbLink> where 1=2;I keep that in mind, thanks for that hint.

SQL Message 207, Severity 16 - Invalid Column Name

The Config Manager 2012 system seems to be very sick with SQL Message 207, Severity 16 - Invalid Column Name messages in the Management Point logs. The column is populated by NULL values. The error message in the logs suggests I refer to the
Config Man, SQL, or Knowledge Base for further details. I've looked around but I'm not really sure if this is a "repairable" problem. Has anyone seen this before and can point me in the direction to a solution? The server is a standalone
Primary.

Hi Niall and Torsten,
Installed in September of last year. Windows Server 2008 R2 Standard, SQL 2008 R2 SP2 (10.50.4000).
The text from the log reads:
Microsoft SQL Server reported SQL message 207, severity 16: [42S22][207][Microsoft][SQL Server Native Client 10.0][SQL Server]Invalid column name 'Distinguished_Name0'.
Please refer to your Configuration Manager documentation, SQL Server documentation, or the Microsoft Knowledge Base for further troubleshooting information.
Followed by:
Discovery Data Manager failed to process the discovery data record (DDR) "D:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box\adsu9110.DDR", because it cannot update the data source.
Possible cause: On a Primary site, it is probably a SQL Server problem.
Solution:
1. Review the immediately preceding status messages from this component about SQL Server errors.
2. Verify that this computer can reach the SQL Server computer.
3. Verify that SQL Server services are running.
4. Verify that the site can access the site database.
5. Verify that the site database, transaction log, and tempdb are not full.
6. Verify that there are at least 50 SQL Server user connections, plus 5 for each Configuration Manager Console.
If the problem persists, check the SQL Server error logs.
Possible cause: On a secondary site, Discovery Data Manager probably cannot write to a file on the site server, so check for low disk space on the site server.
Solution: Make more space available on the site server.
As far as I can tell the services are running, there is no disk space issue, the server can access the database, not sure about the logs or the connections.

Logical model fwd engineer to relational model. Missing FK relationships

We are experiencing missing relationships in the relational model when engineering from logical model to the relational model. The logical model objects have properly defined primary keys defined. We are using SQL Data Modeler v3.1.700. Any suggestions on how to engineering these relationships without deleting the objects from the relational model.
Thanks,
Ed

Hi Ed,
I presume you had some relationships in the Logical Model that you were expecting to be engineered to Foreign Key relationships in the Relational Model.
Please can you provide more detail to help resolve your problem. For example:
Was the problem on an initial engineer from the logical model? Or on a re-engineer?
Are you using Entity subtyping in your Logical Model?
Are there any relevant error messages in the log file? (This is normally file datamodeler.log in folder datamodeler\datamodeler\log.)
David

SDDM EA 3.1: Engineer to Relational Model (subtypes)

It seems that mandatory attributes of entity subtypes become mandatory columns on the corresponding tables even when you engineer to "one table" (the super type).
In that case I would expect that the column would become optional.
Even better: a check constraint would verify that the column was not null for records belonging to the originating subtype.
/ Marc de Oliveira

1) Funny, when I dropped the column, and had it recreated by the engineering process, it worked correctly. But re-engineering the old column kept setting it to mandatory even when I manually set it to optional. I have a sense that some of my objects are ignored by the tool... Only when I drop them and recreate them they seem to be recognized. I had the same issue with some entities that consistenetly did not got engineered into my relational model. Only when I created a new ER-diagram and included the same entities they would get engineered into the relational model...
2) Designer did this. When a supertype table was generated in the "one table" mode there would always be a new column called SUBTYPE with a constraint allowing the short names of each subtype as values (ex: for the table PARTIES the SUBTYPE column could only contain the values PERS and ORG). With this in place you could create constraints such as "SUBTYPE = 'PERS' and FIRST_NAME is not null or SUBTYPE = 'ORG' and FIRST_NAME is null".
Regards,
Marc de Oliveira

Engineer to Relational Model case sensitive?

I developed my database in the Logical Model using Upper and Lower case. When I`m engineering from Logical to Relational Model, it keeps showing me that all atributes have their names wrong and marks them for change in the relational model. Is there a way to inform data modeler to not consider the change in case as differences?

The thing is that in the Relational Model, all objects are beeing generated in uppercase. When I'm going to update the relational model by enineering from Logical, the program always shows me that the column names are different, when they are not, because the only difference is case! There is already a parameter for the engineering not to test for different case in the entity's name, but no parameter for it in the atribute's name!

EA 2.1 - SQL autoformat does not capitalize some column names

Hi,
If I put this bit of SQL into the worksheet, select it, and click the A->a formatting button to cycle through the options:
SeLecT Id, NaMe, MY_SpecIal_Column, yEAr fROm DuAl;
turns into
INITCAP - Select Id, Name, My_special_column, Year From Dual;
UPPER - SELECT ID, NAME, MY_SPECIAL_COLUMN, YEAR FROM DUAL;
LOWER - select id, name, my_special_column, year from dual;
UPPER_KW - SELECT ID, NAME, my_special_column, YEAR FROM dual;;
LOWER_KW_UPPER_ID - select id, name, MY_SPECIAL_COLUMN, year from DUAL;
You can see in the last two cases that ID, NAME, and YEAR are treated as keywords instead of column names.

Hi,
I think it is due to Oracle keywords which can be used as column names.
SQL Dev thinks the column given is a keyword instead of column name.
In my opinion, it works just fine.
In the first place, we should avoid using keywords as column name.
However, as in your case, when we need the column to be formatted as desire,
Perhaps the developer should give some handling over the keywords themselves.
SELECT <to be treated as column> FROM <to be treated> WHERE <to be treated>
UPDATE <to be treated> SET <to be treated> WHERE <to be treated>
CREATE TABLE / VIEW <to be treated>
Wow... that would be a long list of handling.
And it would turn out to be double time efforts on the case conversion though.
Regards,
Buntoro

Warning icon on Engineer to Relational Model screen

Engineer to Relational Mode l shows warning icon on Attributes, Entities and Logical labels. I don't see the reason.
Do you know what this warning icon is about and how to tackle it?
Thanks,
Prakash

Hi Prakash,
Engineer to Relational Mode l shows warning icon on Attributes, Entities and Logical labels. I don't see the reasonThis mean something is changed. You can click on object and should look at details tab. Entity is composite object and it'll get warning mark also if some of components are changed.
At "compare/copy options" tab you can exclude some properties from compare process if you don't want them to be considered.
Philip

SQL Datamodeler: Relational model: column properties: formula description

Hello
When I navigate to the column properties of a formula column I can add a formula description.
This formula description is not picked up by the DDL generator (Oracle).
What am I missing?
Regards Erik

Hi Erik,
if you put something there it will appear on diagram instead of data type (for good or bad). There will be more usage when support for virtual columns in Oracle 11g is implemented.
Best regards,
Philip

SQL Datamodeler 3.0 (Data Modeler 3.0 EA1.)

On the panel 'Structured Types Properties', will be allowed to use a 'Domains' radio button to define the shape of an attribute?
Edited by: user4179829 on Oct 11, 2010 12:24 PM

Scott,
This is one for the feature requests list. You can log requests at sqldeveloper.oracle.com. Please provide a clear explanation of what you request.
Sue

SQL Datamodeler: engineer to relational model: column names

Similar Messages

Maybe you are looking for