Is there any best practices to define a data shape field as INFOTABLE and which is attached to datatable or stream?
What about data consistency and performance of the system?
Any limitation on INFOTABLE field datasets?
Thanks & Regards,
Solved! Go to Solution.
Are you experiencing any particular issues in doing this?
There aren't any specific best practices for infotables in infotables. There are some articles on DataTables and Streams and their limitations that probably is the best I can point to.
Thanks for the response @PaiChung.
In INFOTABLE field dataset how many rows of data can be stored in both DATATABLE and STREAM?
I am going to update frequently at INFOTABLE field dataset. I am facing performance issue? While query and update actions it lagging little bit. Is there any best practices for these kind of scenario.
If you're doing this type of storage, you should definitely consider externalizing your data storage to a custom relational schema. You can do this as a new schema in Postgres or the DB of your choosing. PTC recommends doing this if you anticipate storing more than 250,000 rows of data in a data table or if you have highly relational requirements (which it sounds like you do if you're trying to use an infotable within your datatable/stream).
If one of the previous responses allowed you to resolve your issue, please mark it as the Accepted Solution for the benefit of others with the same question.