[
https://issues.jboss.org/browse/TEIIDDES-715?page=com.atlassian.jira.plug...
]
Barry LaFond commented on TEIIDDES-715:
---------------------------------------
Also note that our DB's (Oracle and SQL Server, whatever) probably don't have the
same "Schema" on them. So if one DB has many more schema and we're fetching
ALL of them (3rd JDBC import page), then it would probably take more time.
Oracle metadata import using Designer takes long time for large
schemas
-----------------------------------------------------------------------
Key: TEIIDDES-715
URL:
https://issues.jboss.org/browse/TEIIDDES-715
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 7.1
Reporter: Ramesh Reddy
Assignee: Dan Florian
Fix For: 7.4
Importing metadata from Oracle database seems to take longer than any other database,
when the underlying the schema is large. This may be because the default settings with
Oracle Driver tries to get lot more metadata then needed. Should explore ways to minimize
the time to take import.
Teiid in the Dynamic VDB import uses "Table Types" and "schema" name
to limit the number of tables it imports, may be we should adopt similar thing in
Designer. It is possible that Designer is already doing such settings.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira