Skip to main content
M
magrawal1-Visitor
1-Visitor
October 14, 2016
Solved

QueryDataTableEntries service fetch result slow.

  • October 14, 2016
  • 2 replies
  • 2247 views

Hi guys,

In my application I've used QueryDataTableEntries service at many places but the problem I am facing with this service is that when I defined it's maxItems to 100000, it is fetching results very slow.

is anyone faced the same issue? how could I optimize response time here?

Thanks,

Meenakshi

Best answer by CarlesColl

Hi,

Here you have an interesting read: https://community.thingworx.com/community/developers/blog/2016/03/11/where-should-i-store-my-thingworx-data#comment-2199

But by the way, if you have DataTables larger than 100k registers, better you go and move those to a real traditional relational database. For instance if you have Postgres TW you can create a table and connect to it through Database Thing, then you will be able to query through traditional SQL.

Carles.

2 replies

C
CarlesColl1-VisitorAnswer
1-Visitor
October 14, 2016

Hi,

Here you have an interesting read: https://community.thingworx.com/community/developers/blog/2016/03/11/where-should-i-store-my-thingworx-data#comment-2199

But by the way, if you have DataTables larger than 100k registers, better you go and move those to a real traditional relational database. For instance if you have Postgres TW you can create a table and connect to it through Database Thing, then you will be able to query through traditional SQL.

Carles.

M
magrawal1-VisitorAuthor
1-Visitor
October 14, 2016

Thanks Carles Coll​, Traditional RDS is the best option for me.

S
supandey5-Regular Member
5-Regular Member
October 14, 2016

Hi Meenakshi, expanding on what Carles already mentioned, indeed it will help you address your concerns - have a look at this JDBC Extensibility and JDBC Connector Extension from ThingWorx Marketplace.

Hope this helps.

Terms & ConditionsAccessibility statement