Object References Report
The object references report provides a general overview of the objects referenced by other objects in the input source code.
Built-in elements are not considered as part of this report.
What is an "Object Reference"?
An object reference is the term used to refer to DDL definitions in the source code, that are being referenced by code units. The table below shows which elements could be referenced in each supported language.
Object | Teradata | Oracle | SQL Server |
---|---|---|---|
Table | ✓ | ✓ | ✓ |
View | ✓ | ✓ | ✓ |
Procedure | ✓ | ✓ | ✓ |
Function | ✓ | ✓ | ✓ |
Macro | ✓ | ||
Package Function | ✓ | ||
Package Procedure | ✓ | ||
*Package | ✓ | ||
Join Index | ✓ | ||
Index | ✓ | ||
Synonym | ✓ | ||
Database Link | ✓ | ||
Type | ✓ | ✓ | ✓ |
Materialized View | ✓ | ||
Trigger | ✓ | ✓ | ✓ |
Sequence | ✓ | ✓ | ✓ |
Constraint | ✓ | ✓ |
If an asterisk ('*') is listed in the section above, it means that the object is used to call properties from itself that are not considered DDL statements such as constants, variables, or cursors.
Where can I find it?
The object references report can be found in a folder named "reports", in the output folder of your conversion. The name of the file itself starts with "ObjectReferences" so it can easily be located.
The format of the file is .CSV.
What information does it contain?
The object references report contains the following information about all the references found while converting:
Column | Description |
---|---|
PartitionKey | The unique identifier of the conversion. |
FileName | The name of the file in which the object is located. |
Caller_CodeUnit | The type of the code unit referencing an existing element. |
Caller_CodeUnit_Database | The database of the code unit referencing an existing element. For now, only SQL Server objects can have a database. |
Caller_CodeUnit_Schema | The schema of the code unit referencing an existing element. |
Caller_CodeUnit_Name | The name of the code unit referencing an existing element. |
Caller_CodeUnit_FullName | The fully qualified name of the object referencing an existing element. |
Referenced_Element_Type | The DDL type of the referenced element. |
Referenced_Element_Database | The database of the referenced element. For now, only SQL Server objects can have a database. |
Referenced_Element_Schema | The schema of the referenced element. |
Referenced_Element_Name | The name of the referenced element. |
Referenced_Element_FullName | The full qualified name of the referenced element. |
Line | The line number inside the file where the reference is located. |
Oracle Database Links as object references
To get the information such as database name, schema name, or object name of database link references, we need to know how the database link was defined. Database links contain the most relevant information in the connection string used in its definition. E.g.
Database Link with database name
Using the example above, the object reference information should look like this:
Caller_CodeUnit | Referenced_Element_Type | Referenced_Element_Database | Referenced_Element_Schema | Referenced_Element_Name | Referenced_Element_FullName | Line |
---|---|---|---|---|---|---|
SELECT | CREATE DATABASE LINK | RemoteDb | N/A | remote_hr_db | hr.employees@remote_hr_db | 6 |
Database Link with database and schema names
Using the example above, the object reference information should look like this:
Caller_CodeUnit | Referenced_Element_Type | Referenced_Element_Database | Referenced_Element_Schema | Referenced_Element_Name | Referenced_Element_FullName | Line |
---|---|---|---|---|---|---|
SELECT | CREATE DATABASE LINK | RemoteDb | MySchema | remote_hr_db1 | hr.employees@remote_hr_db1 | 6 |
Database Link with a connection string
Using the example above, the object reference information should look like this:
Caller_CodeUnit | Referenced_Element_Type | Referenced_Element_Database | Referenced_Element_Schema | Referenced_Element_Name | Referenced_Element_FullName | Line |
---|---|---|---|---|---|---|
SELECT | CREATE DATABASE LINK | MyDB | N/A | remote_hr_db2 | employees@remote_hr_db2 | 6 |
Last updated