Sybase Data object corresponds to structure of tables, views and synonyms in Sybase database. The Sybase data object will always be associated to an Sybase Data point. For details of creating Sybase data point, refer Working with Sybase Data Point. 

To work with Sybase Data Object, follow below steps:

Step I: Edit, create or import an Sybase data object

It is recommended to create data object by importing the structure from the database object.

Step II: Configuring attributes

The Sybase Data Object contains following fields. These fields can be edited by clicking on the field and inputting the required value. When importing the structure directly from the database these fields are auto-populated based on the column properties of the database object.

  • Attribute: Displays the name of the field as in the database object. This is a text field and name can be defined as needed. It is mandatory that the attribute names in data object exactly match the column names of the database object they are referring.
  • Data Type: Displays the datatype associated with the field. This is a list of applicable data types. You can select appropriate type for the field.
  • Precision: Displays the precision for the varchar, number and decimal data type. This is a text field and name can be defined as per the data in the file.
  • Scale: Displays the scale for the number and decimal data type. This is a text field and name can be defined as per the data in the file.
  • Data Sensitivity: This is relevant when data object is used as a source instance. Specify if an attribute has sensitive information and the data in source system is masked. This is required to be specified when the datatype provided in the data object is only indicative of unmasked data and the target structure should map to the datatype for the masked data. You can map the data type of data sensitive attributes to a common datatype in Diyotta Admin's datatype mapping page. For more information, refer Editing Data Type MappingThe drop down provides the category of sensitivity of the data. Below are the categories
  • SPIRSH-Sensitive Personally Identifiable Information with a Real Risk of Significant Harm
    SPII-Sensitive Personally Identifiable Information
    PIIPD-Personally Identifiable Information in the public domain
    PII-Personally Identifiable Information
    PD-Personal Data
  • Not Null: Displays if the field can have NULL values. This is a checkbox and can be defined as per the data in the file. 
  • Key Type: Displays if the field is key field. This is a dropdown with values Primary Key and Foreign key. Select one of these if the field is one of these keys.
  • Unique Primary Index: Unique Primary Index help the SET table to check for duplicates easily rather than comparing entire row under its inspection.
  • Non-Unique Primary Index: When it is not possible to have all unique values to be chosen as a PI, we choose a PI which is almost unique with lesser duplicates as NUPI column. 
  • Unique secondary Index: Unique Secondary Indexes to Enforce Row Uniqueness which perform standard SQL row inserts and updates, are supported for USI-indexed tables.
  • Non-Unique secondary Index: Specified to prevent full-table scans, in which every row of a table is read.
  • Description: Displays any details provided for the field. This is a text field and you can enter any detail as need.


  • Following operations are allowed on the database entries: Add, Cut, Copy, Paste, Up, Down, Delete, and Search.
  • From the list of attributes, multiple attributes can be selected and we can perform/apply these operations.
  • To add a new attribute, click Add. By default a new attribute is populated in the last row. If you want to add an attribute at a specific position then, select the attribute in the position prior to it and click Add.
  • To search for a specific attribute, enter the keyword in the search bar, and the page displays the related attributes.

Step III: Save the changes

To save the changes made to the data object, refer Saving Data Object.


Viewing DDL: 

DDL is generated based on the attributes and their properties in the Attributes tab.

Note: DDL is available only for database-based data objects, and for file-based data objects, the DDL is not available.

Viewing sample Data:

Displays preview of data from the associated object in the database.

Following options are available in View Data tab:

  • By clicking Refresh, the data displayed is reloaded.
  • By clicking Export, the displayed records are exported and saved as excel to default download folder in the machine.

Note: To view, write, and run a SQL query on the Data Object, refer Working with SQL Editor.