Aqua Data Studio 14.0.8
Build #: 35460
Built on: 2014-Jan-09 08:51:14 AM
Database-Teradata Aster
Validation-1
1.Go to ER-Modeler menu,Select New option
New Entity Relationship diagram window is opened,
Select Database name "Teradata Aster" from list under database type pane
In Version Pane all version of selected database is display
Select version and double click on it.
blank Entity Relationship Diagram get opened.
2.In Entity Relationship diagram,go to Palette pane,click on Table entity
move cursor on sheet and click
Table diagram get added in sheet and table name is display as Table_1
double click on Table entity which is in sheet
Table Properties window get opened
In Table Properties window,enter database name and schema name
Add first column of int datataype
Go to Storage Tab
Select Table Type as Fact from drop down list
do not specify column name in Distributed By field
Select Compression Level as COMPRESS HIGH from drop down list
Select Storage Type as Column from drop down list
Click OK,fact table get created but for FACT table type we should specify
column name in Distributed By field that is mandatory but ER diagram no validation was done
Validation-2
1.Go to ER-Modeler menu,Select New option
New Entity Relationship diagram window is opened,
Select Database name "Teradata Aster" from list under database type pane
In Version Pane all version of selected database is display
Select version and double click on it.
blank Entity Relationship Diagram get opened.
2.In Entity Relationship diagram,go to Palette pane,click on Table entity
move cursor on sheet and click
Table diagram get added in sheet and table name is display as Table_1
double click on Table entity which is in sheet
Table Properties window get opened
In Table Properties window,enter database name and schema name
donot add column name
Go to SQL Preview Tab,Create Table script get display but we didn't
added column to table
see attached screenshots
We do some validation on the client side but for most sql generated we allow the GUI's to create what the user is asking for and then display any server sql exceptions back to the user. In this case, you will notice that if you are doing it in ERM it does allow you to create the sql, but when you run the sql it will tell you that DISTRIBUTE BY must be hash() if its a fact table. In the regular tree, the sql is also generated but that ok button actually sends the ddl to the server and then displays the server exception. We do not keep track of all validations for object creation in ERM.