You can also design your sensitive data using Data Modeler.

In table properties you can define a redaction policy for the table:

In column properties (double-click the column name in table properties or press the XYZ icon) select Security.

In this tab you can design two main categories: Redaction and TSDP (Transparent Sensitive Data Protection).

In Redaction section you can define whether or not the column holds personally identifiable information (PII) (YES/NO), whether or not it holds sensitive information (YES/NO), the masking type used (FULL, NO, PARTIAL, RANDOM, REGEXP) and which masking template to use.

You can define your own masking templates by selecting Mask Templates Administration from Tools Menu:

 

After defining them they will be available in the list. Note that they must be of the same datatype as the column itself and of the same masking type selected to be seen on the list.

 

In TSDP section you can define the Sensitive Type used and type in the Sensitive Data Description.

You can define new sensitive types by right-clicking the Sensitive Types in Browser and selecting New Sensitive Type.

 

 

And now back to the Column Properties and the Security Properties. In TSDP Section we can select a Sensitive Type created as a sensitive type for that column, as well as Masking Type and Mask Template:

 

You can also define sensitive type for a Domain:

 

 

You can define new TSDP policies by right-clicking the TSDP Policies in the Browser and selecting New TSDP Policy:

They can include Sub Policies:

with Mask Types and Mask Templates etc.

You can also attach a Sensitive Type to the TSDP Policy:

 

After designing the sensitive data you might want to see a report of it.

The best way to do that is Search and Advanced Mode:

Select Contains sensitive information Property and true.

Now you can see all the columns that have been defined to hold sensitive data.

Press Report and select the format type preferred etc.

And here we are…

 

 

 

I want to compare a DDL and a design using File|Import|DDL File. I know my design is correct but the comparison always shows the DDL to be correct and suggests me to change the design. How to I tell the tool that my design is correct and I want to alter the database accordingly?

It is very simple. While importing the DDL select “Swap target model”

Now the comparison will show the design as the source (truth) and the DDL as the target (false). AND it will give you the ALTER DDLs to change the database. Simply press DDL Preview to get those ALTER scripts.

 

 

I was working on my logical model diagram but now I cannot see that canvas anymore. How can I get it visible again?

Right-click on the Logical Model in the Browser and select Show.

 

 

 

 

 

I would like to have my attributes in alphabetical order. Do I need to do it manually or is there a way to do it automatically?

There is a way to do it automatically. Right-click on the Logical Model canvas and select Sort Attributes. You can sort them either ascending or descending.

 

 

But are you sure you want them to be in alphabetic order? Usually it is easier to understand the model if the primary key attributes are first and usually we define the mandatory attributes in the beginning of the list.

 

 

I have defined several domains but when I try to use them I cannot see any of them in the list. What is wrong?

Most likely the reason is that you have the Preferred property enabled for logical datatypes and when you change to domains it stays enabled. You have not defined any domains and preferred domains and that is why the list is empty.

Either disable Preferred or define the domains as preferred in Preferences.

 

 

I always use surrogates as primary key and I use the Data Modeler functionalities to generate them automatically. That is very good but I do not like that it only defines them as NUMERIC. I have defined a domain I would like to use when generating those primary keys but how can I tell Data Modeler to use that domain?

 

To define the default domain for surrogates go to Preferences, Data Modeler, Model, Relational and select that domain from the list of domains:

 

Now when the tool generates a surrogate primary key it will use the domain definition for it.

 

My colleague is using something she calls Preferred Datatypes when working but I am not sure what she is talking about?

You can define some of the logical datatypes to be your preferred logical datatypes (or preferred domains). In the Preferences you define a list of logical datatypes as preferred logical datatypes like this:

 

Then when designing the attributes you enable Preferred and will only see those logical datatypes, that were defined as preferred, in the list.

 

Now you do not need to go through the whole list of potential logical datatypes, only the ones that you find useful.

 

You have probably already learned that when you change the Logical Model you need to press the double-arrow pointing to right (Engineer to Relational Model) to get those changes to the Relational Model. But with Physical Model it is a different case: you create a Physical Model once and after that the tool will automatically add new object there. You only need to go and define the physical properties for those elements.

If you want, you can define defaults for physical properties. These defaults depend on the RDBMS selected: for example for Oracle they are different than for SQL Server. For Oracle RDBMS you can for example define the default user and the default tablespace.

 

For some of the elements you can also define templates: a set of properties that will be automatically set for a new element of that type. For Oracle RDBMS you can for instance define a template for tables and indexes. Here’s an example of an index template for an Oracle RDBMS:

 

The defaults you define in Preferences will be used to automatically set properties for a new elements of that type. But of course you can manually change them to something different for an individual element.

This functionality is very useful if the element of one type (tables, indexes, …) have some properties always or most of the time the same.

Note: You can also use Propagate Properties to easily copy properties from one element to several elements of the same type.

Note: if you cannot see the Physical Model in the Browser, right-click and select Open.

 

Because a bitmap index is an Oracle specific feature that can only be done in the Physical Model for Oracle RDBMS.

You define the indexes in Relational Model. First go to Table Properties of the table you want to create an index for and press the green plus. Add the information needed.

Then in Physical Model (for Oracle RDBMS) select that index and define it as bitmap index.

When generating the DDL, you will get something like this:

CREATE BITMAP INDEX Orders_Customer_CustNO_IDX ON Orders
(
Customer_CustNO ASC
)
LOGGING ;

 

Note: If you want ALL your indexes in Oracle RDBMS to be bitmap indexes, you can define a template for indexes and set bitmap as a default. First enable the defaults for Oracle Physical Models Index Templates in Preferences:

Then set (Press View/Edit) the default for Bitmap Index as YES.

 

 

 

 

I have defined Primary Key, Unique Key and Foreign Key Constraints and I know I want to have indexes for them. Do I really need to go and define them one by one in Data Modeler? Not necessarily.

Go to Design Properties (double-click the name of the design or right-click and select Properties). Enable all or those you want from Automatic Index Generation.

Now when you generate the DDLs, the DDLs for generating these indexes will be generated automatically.

How are those automatically generated indexes called? You can define that also in Design Properties as the template for Automatic Index.