[teiid-issues] [JBoss JIRA] (TEIID-4021) MSSQL Pagination

[Mark Tawk (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-4021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285286#comment-13285286 ] 

Mark Tawk commented on TEIID-4021:
----------------------------------

The problem is reproduced when having 2 Teiid models, one connected on MSSQL 2012 and the second on MSSQL 2008.

If the first query is executed on MSSQL 2012, Teiid is considering globally that all other MSSQL connections are 2012 and thus the exception sent above is reproduced when running a query on MSSQL 2008 afterward.

If first query is executed on MSSQL 2008, it executes successfully.




> 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)