E1: TDA: FAQ – EnterpriseOne Performance Table Joins And Business Views (Doc ID 2455076.1)

Last updated on DECEMBER 29, 2022

Applies to:

JD Edwards EnterpriseOne Tools - Version 9.1 and later
Information in this document applies to any platform.

This document contains answers to frequently asked questions on EnterpriseOne performance in relation to table joins and business views

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

Purpose

Question 1: EnterpriseOne allows simple join, outer join (left, right), union business view and cross data source join. Which join will have better performance?

Question 2: What is the purpose of an index, FROM clause and WHERE clause in a table join statement?

Question 3: Can an index be created on any column on the table other than the ones shipped by JDE?

Question 4: Why is it important to have an index on columns used in WHERE clause or FROM clause in a table join statement? What will happens if there is no index on the column used in the WHERE clause or FROM clause in a table join statement?

Question 5: How does performance impact if a business view has too many columns in the join select statement?

Question 6: How is performance impacted if there are too many columns in WHERE clause in a table join statement?

Question 7: Why is it important to have matching index of join columns in the WHERE clause in a table join statement?

Question 8: In FDA why is it important to have an index on columns used for search type in information header and grid QBE?

Question 9: What factors can influence performance of a table join or business view?

Question 10. How do you track a long running query and analyze long running query for business view joins in database?

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.