Wonder why using Limit or Top in SQL is sometimes faster than setting Preference Row Limit in Aginity Pro


For example, when you put limit 100 on a SQL statement Aginity Pro passes that exact statement to the database.

SELECT *
FROM AGINITY_DEMO.PUBLIC.LANDING_DIM_CUSTOMER
wherelower(first_name) like$enter_first
limit 100;


When you set your preference we are actually using the JDBC drivers setmaxrows property.  We do this on purpose since each DB has different sql syntax for limits (e.g. top for SQL server limit for other etc..)

 

 

 


We acknowledge and see the time differences as well in our lab tests but have narrowed them down to possibly how the JDBC drivers implement the property.  We will continue to monitor the situation but wanted to educate the community why.

 

Aginity Team

0

Comments

0 comments

Please sign in to leave a comment.

Didn't find what you were looking for?

New post