[
https://issues.jboss.org/browse/TEIID-4021?page=com.atlassian.jira.plugin...
]
Mark Tawk commented on TEIID-4021:
----------------------------------
I'm using teiid embedded, how can I get the source / translator configuration of the
vdb?
Otherwise, i have debugged into SQLServerExecutionFactory.java; in fact, when executing
the first MSSQL query it is assigning MSSQL version in initCapabilities method. And it is
keeping the same value version property for the next executed mssql queries without
reassigning it from the used connection.
In my case, the property "version" in SQLServerExecutionFactory class is
assigned to "11.0.2100" for mssql 2012, and when running a query on mssql 2008,
"version" property is not reassigned and it keeps using the initial value
"11.0.2100".
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)