# Query Browser

**URL:** <https://forum.inductiveautomation.com/t/query-browser/5550>\
**Category:** Ignition\
**Created:** [December 10, 2012, 10:24am UTC](https://forum.inductiveautomation.com/t/query-browser/5550 "2012-12-10T10:24:14Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://forum.inductiveautomation.com/u/Ivan)\
**Post date:** [December 10, 2012, 10:24am UTC](https://forum.inductiveautomation.com/t/query-browser/5550/1 "2012-12-10T10:24:14Z")

</div>

Hello everyone,

Why is the query browser limited to 1000 rows?

Thanks,

Ivan

---

<div class="post-metadata">

**Author:** ![nathan](https://avatars.discourse-cdn.com/v4/letter/n/c5a1d2/32.png) [@nathan](https://forum.inductiveautomation.com/u/nathan)\
**Post date:** [December 10, 2012, 10:48am UTC](https://forum.inductiveautomation.com/t/query-browser/5550/2 "2012-12-10T10:48:19Z")

</div>

I’m not on a machine where I can test it, but according to [this thread](http://www.inductiveautomation.com/forum/viewtopic.php?f=70&t=7111), it appears that increasing the limit in your query (with the LIMIT or TOP keyword) will increase the number of rows displayed in the results, but that there is currently no way to adjust the default row limit in the Ignition Query Browser.

In other words, the Query Browser adds a “LIMIT 1000 / TOP 1000” to your query if you do not specify one. I imagine this was done to protect you from unintentionally running slow queries on huge tables.

---

<div class="post-metadata">

**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://forum.inductiveautomation.com/u/Ivan)\
**Post date:** [December 14, 2012, 1:17pm UTC](https://forum.inductiveautomation.com/t/query-browser/5550/3 "2012-12-14T13:17:26Z")

</div>

This would explain it, thanks.  
I should have searched the forum as I usually do, so please delete this useless topic!

---

<div class="post-metadata">

**Author:** ![eklockziem](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/eklockziem/32/12175_2.png) [@eklockziem](https://forum.inductiveautomation.com/u/eklockziem)\
**Post date:** [December 23, 2019, 4:32pm UTC](https://forum.inductiveautomation.com/t/query-browser/5550/4 "2019-12-23T16:32:24Z")

</div>

I am using an Oracle Database, and it does not accept a LIMIT Clause. When Using the Browser, I can get the return data to look EXACTLY how I want it by choosing the Limit to be 10. Does anyone know what clause the Browser creates for a LIMIT in an Oracle DB?

---

<div class="post-metadata">

**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\
**Post date:** [December 23, 2019, 4:41pm UTC](https://forum.inductiveautomation.com/t/query-browser/5550/5 "2019-12-23T16:41:48Z")

</div>

I think this is what you’re looking for:

`WHERE ROWNUM <= 10`

---

<div class="post-metadata">

**Author:** ![eklockziem](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/eklockziem/32/12175_2.png) [@eklockziem](https://forum.inductiveautomation.com/u/eklockziem)\
**Post date:** [December 23, 2019, 6:23pm UTC](https://forum.inductiveautomation.com/t/query-browser/5550/6 "2019-12-23T18:23:19Z")

</div>

Thanks!!

Had to run a subquery with the ORDER BY first, and then apply ROWNUM \<= 10, in order to display the return values properly.