I am designing a new driver that contains a very large table (up to 50,000 rows). Rather than splitting the table, I am considering using partial table <ArrayOptions partial="true:2000">.
I know there were some limitations in the past associated to partial tables e.g. sorting, filtering, alarming but many of those issues have been solved in recent versions of DataMiner.
Assuming I am using the latest DataMiner version, what disadvantages are still present when using partial tables when it comes to filtering, sorting, visio, monitoring, other.
Thanks in advance,
For partial tables, the client only has the active page in memory. Any action that applies to the full data set (sorting, filtering), will result in updated subscriptions to the server. Depending on the amount of data, the load on the server and the network between client and server, this may introduce some delay. Partial tables have no effect on monitoring: alarm monitoring happens on the server, where all data is available.
The big advantage of partial tables is that the client memory usage will be significantly lower. Also UI responsiveness will be better if the amount of rows in client memory is limited to max a few thousand. Tables in Visio use the same component as in data display, so the same advantage and disadvantage applies there as well.
In general, we advise to make a table partial if the number of rows can get bigger than a few thousand. In this case it's important to set good default sorting, so the first page is likely to be the most interesting page for the user.