[teiid-designer-issues] [JBoss JIRA] Commented: (TEIIDDES-715) Oracle metadata import using Designer takes long time for large schemas

[ https://issues.jboss.org/browse/TEIIDDES-715?page=com.atlassian.jira.plug... ] Dan Florian commented on TEIIDDES-715: -------------------------------------- Before the import wizard's finish button is clicked, the SQL Server importer is taking *WAY* more time than the oracle importer. When you consider the total import time (going through the wizard pages and finishing the wizard), Oracle is much faster than SQL Server. The major difference is the time it takes to display the JdbcImportMetadataPage. In Oracle, the JdbcImportMetadataPage wizard page takes less than a second to display. But in SQL Server, that same wizard page takes around 17-18 seconds. It appears the SQL Server importer is fetching much more metadata up front while Oracle much more at the end of the wizard. For instance, prior to finishing the wizard, the SQL Server importer calls DatabaseMetaData.getSchemas() *LOTS* of times while the Oracle importer only calls it once. One last thing, and not sure if this is important, but the execution code paths of the wizard does diverge based on if the DB "supports catalogs." SQL Server does "supportCatalogs" and Oracle does not. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira