[
https://issues.jboss.org/browse/TEIID-4021?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-4021:
---------------------------------------
The assumption is that a single translator connects to a single source/version. However
in the case of translators that auto-configure to the given version you are expecting that
we'll manage creating new instances when necessary correct? Can you log something for
that?
Another workaround is to add multiple executionfactory instances to allow for each to be
configured independently.
MSSQL Pagination
----------------
Key: TEIID-4021
URL:
https://issues.jboss.org/browse/TEIID-4021
Project: Teiid
Issue Type: Enhancement
Components: JDBC Connector
Reporter: Mark Tawk
Assignee: Steven Hawkins
Fix For: 9.1
I'm using Teiid 8.11.3 with mssql translator.
I have a huge table over sql server 2008 on which i'm applying pagination.
I noticed slowliness in the query execution over this table at each time I increase the
pagination.
I monitored the JDBC queries execute by teiid and found out that it is using top n
according to the limit used into the query.
For example:
in teiid : Select * from mytable LIMIT 90 , 10
is translated in JDBC: select top 100 from mytable
Since my table contains millions of records, when fetching the last page, the executed
jdbc query is retrieving the whole table top n, to return in result the last 10 records.
And the execution is taking too much time.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)